Triple
T31687097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dot Tattler |
E808689
|
entity |
| Predicate | isConjoinedTwinWith |
P69978
|
FINISHED |
| Object | Bette Tattler |
—
|
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: Bette Tattler | Statement: [Dot Tattler, isConjoinedTwinWith, Bette Tattler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConjoinedTwinWith Context triple: [Dot Tattler, isConjoinedTwinWith, Bette Tattler]
-
A.
hasTwin
Indicates that one entity is a twin of another, sharing the same birth event or time with a sibling.
-
B.
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.
-
C.
isTwinWith
chosen
Indicates that two entities are twins, sharing the same birth parents and being born at (or very near) the same time.
-
D.
twinning
Indicates that two entities are paired or linked as twins, typically sharing a formally recognized, parallel, or closely matched relationship.
-
E.
hasOlderTwins
Indicates that an entity has twin siblings who are older than it.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 30, 2026, 11:07 p.m.