Triple
T25741284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacDuff’s hill |
E648223
|
entity |
| Predicate | personalNameElement |
P24312
|
FINISHED |
| Object | MacDuff |
—
|
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: MacDuff | Statement: [MacDuff’s hill, personalNameElement, MacDuff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: personalNameElement Context triple: [MacDuff’s hill, personalNameElement, MacDuff]
-
A.
nameElement
Indicates that one entity serves as the name or label assigned to another entity or element.
-
B.
nameElementIn
Indicates that an entity is (or contains) a specific name element within a larger naming structure or system.
-
C.
isPersonalName
chosen
Indicates that the value is a personal name identifying an individual person.
-
D.
fullName
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
-
E.
namedPersonField
Indicates that a particular data field is designated to contain a person’s name.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd1a238881909e59c4ee479f21dc |
completed | May 2, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 3:43 a.m.