Triple
T17911996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legion of Super-Heroes |
E447837
|
entity |
| Predicate | teamBaseEra |
P127432
|
FINISHED |
| Object | 30th century |
—
|
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: 30th century | Statement: [Legion of Super-Heroes, teamBaseEra, 30th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamBaseEra Context triple: [Legion of Super-Heroes, teamBaseEra, 30th century]
-
A.
homeTeamDuringEra
Indicates that a particular team served as the primary or official home team for an entity during a specified era or time period.
-
B.
associatedWithTeamEra
chosen
Indicates a relationship where an entity is linked to a specific period or era of a team’s history or existence.
-
C.
teamDivisionOrEra
Indicates the specific division or historical era within which a team is categorized or competed.
-
D.
teamStartYear
Indicates the year in which an entity (such as a person or organization) began its association with a particular team.
-
E.
helpedTransformTeamEra
Indicates that an entity played a significant role in changing or defining a distinct period or era in a team’s development or performance.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49ea0ea008190b54a999e0704fb67 |
completed | April 19, 2026, 9:21 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.