Triple
T373404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coptic Rite |
E8317
|
entity |
| Predicate | vestmentStyle |
P13036
|
FINISHED |
| Object | distinctive Coptic clerical vestments |
—
|
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: distinctive Coptic clerical vestments | Statement: [Coptic Rite, vestmentStyle, distinctive Coptic clerical vestments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vestmentStyle Context triple: [Coptic Rite, vestmentStyle, distinctive Coptic clerical vestments]
-
A.
investmentType
Indicates the specific category or nature of an investment associated with an entity or transaction.
-
B.
investmentPhilosophy
Indicates the guiding principles or approach that an entity follows when making investment decisions.
-
C.
riskProfile
Indicates the level and characteristics of potential risk associated with an entity, action, or situation.
-
D.
sectorWeighting
Indicates the proportion or emphasis assigned to a particular sector within a broader portfolio, index, or classification.
-
E.
funds
Indicates that one entity provides financial resources or monetary support to another entity or activity.
- F. None of above. chosen
Provenance (4 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec018d508190b5687a9ba90b3092 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e96216048190873ae533fa5b864d |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ebcb1b2c8190a68bb3bad600c227 |
completed | Feb. 28, 2026, 1:21 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.