Triple
T37716660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star-Spangled Comics #7 |
E939469
|
entity |
| Predicate | introducesCharacterTeam |
P196339
|
FINISHED |
| Object | Newsboy Legion |
—
|
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: Newsboy Legion | Statement: [Star-Spangled Comics #7, introducesCharacterTeam, Newsboy Legion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducesCharacterTeam Context triple: [Star-Spangled Comics #7, introducesCharacterTeam, Newsboy Legion]
-
A.
introducedTeam
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.
mainProtagonistTeamMember
Indicates that an entity is a member of the primary team or group associated with the main protagonist.
-
C.
introducesSeriesCharacters
Indicates that an entity is responsible for first presenting or bringing specific characters into a series.
-
D.
introducesCharacterGroup
chosen
Indicates that an entity presents or brings a group of characters into the narrative or context for the first time.
-
E.
aboutTeam
Indicates that something concerns, relates to, or is associated with a particular team.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: May 3, 2026, 4:18 p.m.