Triple
T7136744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Boyle, 4th Earl of Orrery |
E166323
|
entity |
| Predicate | nameCommemoratedIn |
P7860
|
FINISHED |
| Object | orrery |
—
|
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: orrery | Statement: [Charles Boyle, 4th Earl of Orrery, nameCommemoratedIn, orrery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameCommemoratedIn Context triple: [Charles Boyle, 4th Earl of Orrery, nameCommemoratedIn, orrery]
-
A.
commemoratedFor
Indicates that one entity is honored, remembered, or celebrated because of a particular action, achievement, event, or characteristic associated with it.
-
B.
commemoratedPerson
chosen
Indicates that the subject serves as a memorial or tribute to the referenced person.
-
C.
eraCommemorated
Indicates that a particular era or historical period is honored, remembered, or marked by a commemorative act, object, or event.
-
D.
commemoratedBy
Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
-
E.
hasTypeOfPersonCommemorated
Indicates that something is associated with or dedicated to a person of a specified type or role being commemorated.
- 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_69c68884a9388190af42f90d1c1a7151 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e6926d748190bc8c150fc1860531 |
completed | March 27, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:45 p.m.