Triple
T30813878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fantastic Four #1 |
E784719
|
entity |
| Predicate | featuresTeamDebut |
P110977
|
FINISHED |
| Object | Fantastic Four |
—
|
NE NERFINISHED |
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: Fantastic Four | Statement: [Fantastic Four #1, featuresTeamDebut, Fantastic Four]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresTeamDebut Context triple: [Fantastic Four #1, featuresTeamDebut, Fantastic Four]
-
A.
notableTeamDebut
Indicates the team for which an entity (typically an athlete) made a debut that is considered particularly significant or noteworthy.
-
B.
featuredTeamDebutLeague
Indicates the league in which a team made its first official appearance as a featured or primary team.
-
C.
debutingTeam
chosen
Indicates that an entity is the team for which another entity (such as a player or work) is making its first official appearance or debut.
-
D.
debutantTeam
Indicates that a team is participating in a competition, league, or event for the first time.
-
E.
managerDebutTeam
Indicates the team for which a person made their debut as a manager.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a002e71bdc48190b922f2d3b362d259 |
completed | May 10, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_6a002e1a28708190b65f9e657c770bab |
completed | May 10, 2026, 7:04 a.m. |
Created at: April 29, 2026, 8:43 p.m.