Triple
T8903036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Missal |
E211975
|
entity |
| Predicate | hasDetail |
P33357
|
FINISHED |
| Object | elaborate costume |
—
|
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: elaborate costume | Statement: [The Missal, hasDetail, elaborate costume]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDetail Context triple: [The Missal, hasDetail, elaborate costume]
-
A.
hasEventDetail
chosen
Indicates that an event is associated with additional descriptive information or specific attributes that further characterize it.
-
B.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
C.
hasRich
Indicates that an entity possesses or is characterized by a high level of wealth, abundance, or valuable resources.
-
D.
hasPart
Indicates that one entity is a component, segment, or constituent part of another entity.
-
E.
hasImplementationDetail
Indicates that one entity specifies or contains a concrete implementation detail or internal mechanism related to another entity.
- 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_69ca839255248190b43984294abd92ae |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc64c091d08190b59e54eb4a184e41 |
completed | April 1, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:55 p.m.