Triple
T11669455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Raven |
E277338
|
entity |
| Predicate | associatedTeamEra |
P9671
|
FINISHED |
| Object | World War II-era Invaders |
—
|
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: World War II-era Invaders | Statement: [Red Raven, associatedTeamEra, World War II-era Invaders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedTeamEra Context triple: [Red Raven, associatedTeamEra, World War II-era Invaders]
-
A.
associatedWithPlayerEra
Indicates a relationship where something is linked or connected to a specific era or period in a player's career.
-
B.
homeTeamDuringEra
Indicates that a particular team served as the primary or official home team for an entity during a specified era or time period.
-
C.
team2ChampionshipEraOverlap
Indicates that the second team’s active period overlaps in time with the first team’s championship era.
-
D.
teamDivisionOrEra
Indicates the specific division or historical era within which a team is categorized or competed.
-
E.
associatedTeam
chosen
Indicates that one entity is linked or connected to a particular team, typically as its member, owner, or primary affiliation.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a440d8a481909a13c97813408bc8 |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.