Triple
T36344802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smith family |
E895033
|
entity |
| Predicate | sharesSurnameAmongMembers |
P148237
|
FINISHED |
| Object | Smith |
—
|
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: Smith | Statement: [Smith family, sharesSurnameAmongMembers, Smith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesSurnameAmongMembers Context triple: [Smith family, sharesSurnameAmongMembers, Smith]
-
A.
sharesSurnameWithMany
Indicates that an entity has the same surname as a large number of other entities.
-
B.
hasLastNameInCommonWith
Indicates that two entities share the same last name.
-
C.
familyNameOfMembers
chosen
Indicates that the specified family name is shared by the members of a given group or family.
-
D.
associatedSurname
Indicates that one entity has a surname that is linked or connected to another entity, such as a person, family, or name record.
-
E.
belongsToFamilyCommonName
Indicates that an entity is associated with, or classified under, a particular family-level common 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a008b8938608190adaccbd720111a18 |
completed | May 10, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_6a008b24baac8190baaaf50c2e9cc6bd |
completed | May 10, 2026, 1:41 p.m. |
Created at: May 3, 2026, 4:09 p.m.