Triple
T36597267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ark of Saint Dominic |
E902834
|
entity |
| Predicate | dedicatedToOrder |
P1283
|
FINISHED |
| Object | Order of Preachers |
—
|
NE NERFINISHED |
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: Order of Preachers | Statement: [Ark of Saint Dominic, dedicatedToOrder, Order of Preachers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dedicatedToOrder Context triple: [Ark of Saint Dominic, dedicatedToOrder, Order of Preachers]
-
A.
dedicatedToBrand
Indicates that something (such as a resource, activity, or feature) is exclusively or primarily allocated or committed to a specific brand.
-
B.
refersToOrder
Indicates that one entity makes reference to, or is associated with, a specific order.
-
C.
holdsToOrder
Indicates that one entity is obligated or committed to comply with, fulfill, or act according to an order issued by another entity.
-
D.
dedicated
chosen
Indicates that one entity is formally assigned, reserved, or committed for the specific use, benefit, or purpose of another entity.
-
E.
isOrderedTo
Indicates that one entity has been formally directed or commanded to perform an action or fulfill a duty by another authority.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.