Triple
T19995248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catholic Church (local and devotional) |
E494175
|
entity |
| Predicate | isExpressedBy |
P4750
|
FINISHED |
| Object | lay Catholics |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: lay Catholics | Statement: [Catholic Church (local and devotional), isExpressedBy, lay Catholics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExpressedBy Context triple: [Catholic Church (local and devotional), isExpressedBy, lay Catholics]
-
A.
hasExpressiveRole
Indicates that an entity serves a communicative or expressive function or role in relation to another entity or context.
-
B.
hasExpressivity
Indicates that one entity possesses a certain level or type of expressive power, capability, or richness in representation relative to another.
-
C.
expressedOn
Indicates that something (such as a feature, marker, or characteristic) is present or manifested on a particular entity or surface.
-
D.
expresses
chosen
Indicates that one entity conveys, communicates, or articulates a thought, feeling, or idea through another medium or form.
-
E.
oftenExpressedAs
Indicates that one thing is frequently represented, stated, or manifested in the form of another.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fe3fb288190a935c334e8a5d54e |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:31 p.m.