Triple
T37717854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defenders (Marvel Comics team) |
E939502
|
entity |
| Predicate | originalCoreRoster |
—
|
GENERATED |
| Object | Doctor Strange |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
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 (1 batch)
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. |
Created at: May 3, 2026, 4:18 p.m.