Triple
T30675513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-New X-Men (comic series) |
E780897
|
entity |
| Predicate | teamLineup |
P170005
|
FINISHED |
| Object | Original five X-Men displaced in time |
—
|
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: Original five X-Men displaced in time | Statement: [All-New X-Men (comic series), teamLineup, Original five X-Men displaced in time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamLineup Context triple: [All-New X-Men (comic series), teamLineup, Original five X-Men displaced in time]
-
A.
leagueTeam2
Indicates that the subject entity is the second team participating in a particular league, matchup, or league-related context.
-
B.
leagueTeam
Indicates that a team is a member or participant of a particular league.
-
C.
leagueTeam1
Indicates that the subject is the first (or primary) team participating in a particular league or league matchup.
-
D.
managerTeam1
Indicates that an entity serves as the manager or leader of a specific team (team1) within an organization.
-
E.
fieldsTeam
Indicates that an entity is a member of, or associated as part of, a particular team.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b17a7608190a6568c48d8128dfe |
completed | May 2, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:32 p.m.