Triple
T25994008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward Boone |
E646435
|
entity |
| Predicate | surnameAssociation |
P49952
|
FINISHED |
| Object | Boone family |
—
|
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: Boone family | Statement: [Edward Boone, surnameAssociation, Boone family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surnameAssociation Context triple: [Edward Boone, surnameAssociation, Boone family]
-
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.
namedPersonAssociation
Indicates a relationship where one entity is associated with or identified by a specific personal name.
-
D.
familyNameRefersTo
Indicates that a specified family name designates or refers to a particular person, group, or lineage.
-
E.
notableFamilyNameOf
Indicates that a particular family name is notably or prominently associated with a given person or family 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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6054a859481908aa7275ec4859e4b |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:57 a.m.