Triple
T17886437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Star Comics #3 |
E447211
|
entity |
| Predicate | teamRosterDepiction |
P129149
|
FINISHED |
| Object | founding lineup of the Justice Society of America |
—
|
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: founding lineup of the Justice Society of America | Statement: [All Star Comics #3, teamRosterDepiction, founding lineup of the Justice Society of America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamRosterDepiction Context triple: [All Star Comics #3, teamRosterDepiction, founding lineup of the Justice Society of America]
-
A.
teamRepresentation
Indicates that one entity serves as the official representative or embodiment of a team in a given context or activity.
-
B.
fieldsTeam
Indicates that an entity is a member of, or associated as part of, a particular team.
-
C.
leagueTeam2
Indicates that the subject entity is the second team participating in a particular league, matchup, or league-related context.
-
D.
representedByTeam
Indicates that an entity is officially or formally represented by a specific team.
-
E.
roleAtSportsTeam
Indicates the specific position or function an individual holds within a sports 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49c13bd288190a0302010ba4d0532 |
completed | April 19, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:18 a.m.