Triple
T36957712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vorticons |
E914230
|
entity |
| Predicate | grandIntellectIdentity |
P189378
|
FINISHED |
| Object | Mortimer McMire |
—
|
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: Mortimer McMire | Statement: [Vorticons, grandIntellectIdentity, Mortimer McMire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grandIntellectIdentity Context triple: [Vorticons, grandIntellectIdentity, Mortimer McMire]
-
A.
globalIdentity
Indicates that two or more identifiers or representations actually refer to the same underlying global entity or individual.
-
B.
publicIdentity
Indicates that an entity’s outward-facing identity or persona is known, presented, or recognized in a public context.
-
C.
intellectualRole
Indicates that an entity holds or performs a specific intellectual function, capacity, or responsibility in relation to another entity or work.
-
D.
identityShapedBy
Indicates that one entity’s identity is influenced, formed, or defined by another entity or factor.
-
E.
typicalIdentity
Indicates that one entity is the standard, characteristic, or most representative identity of another entity within a given context.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbc48b75c8190bec27dd4b7de797f |
completed | May 6, 2026, 10:10 p.m. |
Created at: May 3, 2026, 4:13 p.m.