Triple
T17723813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leslie Hamilton Gearren |
E442406
|
entity |
| Predicate | hasTwinType |
P42171
|
FINISHED |
| Object | identical twin |
—
|
LITERAL FINISHED |
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: identical twin | Statement: [Leslie Hamilton Gearren, hasTwinType, identical twin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTwinType Context triple: [Leslie Hamilton Gearren, hasTwinType, identical twin]
-
A.
hasTwinFeature
Indicates that two entities share an identical or nearly identical feature, characteristic, or component, as if they are twins in that respect.
-
B.
hasTwinStructureWith
Indicates that two entities share an identical or nearly identical structural form, typically as corresponding or mirrored counterparts.
-
C.
hasTwinStatus
Indicates that an entity has a twin relationship or classification, such as being one of a pair of twins or having an associated twin counterpart.
-
D.
hasTwin
Indicates that one entity is a twin of another, sharing the same birth event or time with a sibling.
-
E.
twinType
chosen
Indicates that one entity is classified as a specific type or category of twin in relation 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4748900608190bf5ba04415edaffc |
completed | April 19, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:07 a.m.