Triple
T20697182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giant-Size X-Men #1 |
E508687
|
entity |
| Predicate | introducesTeam |
P43992
|
FINISHED |
| Object | new international X-Men team |
—
|
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: new international X-Men team | Statement: [Giant-Size X-Men #1, introducesTeam, new international X-Men team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducesTeam Context triple: [Giant-Size X-Men #1, introducesTeam, new international X-Men team]
-
A.
introducedTeam
chosen
Indicates that one entity formally presented or brought another entity (a team) to the attention of a third party or context for the first time.
-
B.
aboutTeam
Indicates that something concerns, relates to, or is associated with a particular team.
-
C.
introducedTeamColor
Indicates that an entity is responsible for introducing or establishing a particular team color for a team or group.
-
D.
teamComponent
Indicates that one entity functions as a component, member, or sub-unit within a larger team or group entity.
-
E.
exampleTeam
Indicates that an entity is a representative or illustrative member of a particular team or group.
- 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_69e6c1123d7c81908a1d16923437266d |
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.