Triple
T31100684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Superman |
E792663
|
entity |
| Predicate | sharesIdentityAspectWith |
P197926
|
FINISHED |
| Object | Dr. Manhattan |
—
|
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: Dr. Manhattan | Statement: [The Superman, sharesIdentityAspectWith, Dr. Manhattan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesIdentityAspectWith Context triple: [The Superman, sharesIdentityAspectWith, Dr. Manhattan]
-
A.
sharesIdentityWith
Indicates that two entities are considered to have the same identity, referring to the very same underlying individual or object rather than merely being similar or related.
-
B.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
C.
sharesFieldWith
Indicates that two entities are involved in or associated with the same field, discipline, or area of specialization.
-
D.
sharesRoleWith
Indicates that two entities hold the same role or position within a given context or system.
-
E.
sharesAppearanceTraitWith
Indicates that two entities possess at least one similar or matching visual or appearance-related characteristic.
- F. None of above. chosen
Provenance (4 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69feba0f09508190b3e871c62b19ec7f |
completed | May 9, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69feb957fe7c8190969fb31a6d1a59c8 |
completed | May 9, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69feba0e362c81909883a3f24a4a9545 |
completed | May 9, 2026, 4:37 a.m. |
Created at: April 29, 2026, 9:03 p.m.