Triple
T25796340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barcaldine |
E649694
|
entity |
| Predicate | famousDescendant |
P159821
|
FINISHED |
| Object | Sir Visto |
—
|
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: Sir Visto | Statement: [Barcaldine, famousDescendant, Sir Visto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousDescendant Context triple: [Barcaldine, famousDescendant, Sir Visto]
-
A.
famousIndividual
Indicates that an individual is widely known and recognized by a large number of people, typically for notable achievements, status, or public visibility.
-
B.
famousMember
Indicates that an entity is a well-known or widely recognized member of a particular group, organization, or category.
-
C.
fatherNotableFor
Indicates that a person's father is recognized or distinguished for a particular achievement, role, or characteristic.
-
D.
familyNotableMember
Indicates that a particular individual is a distinguished or noteworthy member of a given family.
-
E.
notableFamilyIn
Indicates that a person is notably associated with or belongs to a particular family within a given place or context.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 22, 2026, 6:30 a.m.