Triple
T37717854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defenders (Marvel Comics team) |
E939502
|
entity |
| Predicate | originalCoreRoster |
P204357
|
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: [Defenders (Marvel Comics team), originalCoreRoster, Doctor Strange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalCoreRoster Context triple: [Defenders (Marvel Comics team), originalCoreRoster, Doctor Strange]
-
A.
rosterBasis
Indicates the underlying criterion or rule used to determine which entities are included on a particular roster.
-
B.
rosterControl
Indicates a relationship where one entity manages, configures, or oversees the composition and changes of a group or roster of other entities.
-
C.
coreTeam
Indicates that an entity is a primary, central member of a core group responsible for key decisions or activities within an organization or project.
-
D.
rosterRequirement
Indicates that one entity specifies or imposes a required composition, number, or type of participants that must be included in another entity’s roster.
-
E.
typicalRosterSource
Indicates that one entity is the usual or standard source from which the other entity’s roster or list of members is derived.
- F. None of above. chosen
Provenance (5 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40f1713ab88190afc9adaacfb599ed |
completed | June 28, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.