Triple
T14329391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Another Me |
E355300
|
entity |
| Predicate | hasDoppelgangerElement |
P84501
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Another Me, hasDoppelgangerElement, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDoppelgangerElement Context triple: [Another Me, hasDoppelgangerElement, yes]
-
A.
hasDoppelgangerTheme
chosen
Indicates that something features or involves a doppelganger-related theme, such as doubles, look-alikes, or mirrored identities.
-
B.
hasTwinFeature
Indicates that two entities share an identical or nearly identical feature, characteristic, or component, as if they are twins in that respect.
-
C.
hasDouble
Indicates that an entity possesses or is associated with a counterpart that is a duplicate or closely similar version of it.
-
D.
hasTwinStructureWith
Indicates that two entities share an identical or nearly identical structural form, typically as corresponding or mirrored counterparts.
-
E.
hasDoublesPartner
Indicates that one entity serves as the doubles partner of another in a paired or team-based activity or sport.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8c1def0081908f03cda8e84d20c0 |
completed | April 14, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:13 a.m.