Triple
T36014804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EA Tiburon |
E1041807
|
entity |
| Predicate | developsLicensedGamesFor |
P167548
|
FINISHED |
| Object | National Football League |
—
|
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: National Football League | Statement: [EA Tiburon, developsLicensedGamesFor, National Football League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developsLicensedGamesFor Context triple: [EA Tiburon, developsLicensedGamesFor, National Football League]
-
A.
gameDeveloperPartner
chosen
Indicates a partnership relationship where one entity collaborates with another in developing or producing a game.
-
B.
developerOfContainingGame
Indicates that an entity is the developer responsible for creating the game that contains the referenced element or component.
-
C.
hasDevelopmentStudioIn
Indicates that an entity has a development studio located in a specified place.
-
D.
developedGameBasedOn
Indicates that one game was created or designed using another game as its source of inspiration, foundation, or reference.
-
E.
gameGenreDeveloped
Indicates that a particular game genre has been created, defined, or developed by a specific entity (such as a person, team, or organization).
- 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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: May 3, 2026, 4:07 p.m.