Triple
T25636995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Boone |
E642727
|
entity |
| Predicate | surnameAssociatedWith |
P49952
|
FINISHED |
| Object | American frontiersman Daniel Boone |
—
|
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: American frontiersman Daniel Boone | Statement: [James Boone, surnameAssociatedWith, American frontiersman Daniel Boone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surnameAssociatedWith Context triple: [James Boone, surnameAssociatedWith, American frontiersman Daniel Boone]
-
A.
surnameAssociatedWithField
Indicates that a particular surname is commonly linked or connected to a specific professional, academic, or activity-related field.
-
B.
associatedSurname
chosen
Indicates that one entity has a surname that is linked or connected to another entity, such as a person, family, or name record.
-
C.
surnameUsedIn
Indicates that a particular surname is used or borne within a specified context, such as by a person, family, or group.
-
D.
sharesSurnameWithMany
Indicates that an entity has the same surname as a large number of other entities.
-
E.
associatedName
Indicates that one entity has an alternative or related name that is linked or connected 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa6345548190a52498ecb0a2f555 |
completed | May 2, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:33 p.m.