Triple
T38069790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eternity |
E950562
|
entity |
| Predicate | primaryAssociatedTitle |
P196413
|
FINISHED |
| Object | Doctor Strange |
E45471
|
NE 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: Doctor Strange | Statement: [Eternity, primaryAssociatedTitle, Doctor Strange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAssociatedTitle Context triple: [Eternity, primaryAssociatedTitle, Doctor Strange]
-
A.
associatedTitle
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another entity.
-
B.
primaryTagTitleOf
chosen
Indicates that one entity serves as the main or primary title associated with another entity’s tag.
-
C.
associatedTitleType
Indicates the type or category of a title that is linked or related to another entity or primary title.
-
D.
primaryName
Indicates that the associated name is the main or most commonly used name for the entity in question.
-
E.
primaryUserTitle
Indicates the main professional or role-based title associated with a user in a given context.
- F. None of above.
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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a415d3f601081909098f84ec841dcaa |
completed | June 28, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.