Triple
T20697310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X-Treme X-Men |
E508689
|
entity |
| Predicate | teamAlignment |
P9671
|
FINISHED |
| Object | hero |
—
|
LITERAL 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: hero | Statement: [X-Treme X-Men, teamAlignment, hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamAlignment Context triple: [X-Treme X-Men, teamAlignment, hero]
-
A.
teamLoyalty
Indicates a relationship where an individual consistently supports, commits to, and prioritizes the interests of a particular team over alternatives.
-
B.
associatedTeam
chosen
Indicates that one entity is linked or connected to a particular team, typically as its member, owner, or primary affiliation.
-
C.
teamStrength
Indicates the comparative overall capability or power level of a team, often used to assess how strong one team is relative to others.
-
D.
seasonAlignment
Indicates how the timing or characteristics of one entity’s season correspond, match, or are synchronized with those of another entity.
-
E.
associatedTeamName
Indicates the name of the team that is linked or connected to a given entity.
- F. None of above.
Provenance (3 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_69e0b4c2b2a481909e31e9cb8f81ab55 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c1132178819081086e085f7b3ff8 |
completed | April 21, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:11 p.m.