Triple
T36957214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unreal |
E914217
|
entity |
| Predicate | expansionDeveloper |
P187231
|
FINISHED |
| Object | Legend Entertainment |
—
|
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: Legend Entertainment | Statement: [Unreal, expansionDeveloper, Legend Entertainment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionDeveloper Context triple: [Unreal, expansionDeveloper, Legend Entertainment]
-
A.
laterDeveloper
Indicates that one developer’s work, role, or involvement occurs after another developer in time.
-
B.
expansionPack
Indicates that one item serves as an add-on or supplementary content package that extends the features or scope of another item.
-
C.
expansionProject
Indicates a project whose primary purpose is to enlarge, extend, or increase the capacity, scope, or reach of something.
-
D.
developerOfContainingGame
Indicates that an entity is the developer responsible for creating the game that contains the referenced element or component.
-
E.
gameDeveloper
Indicates that one entity creates, designs, or develops the other entity, which is a game.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb34e4906c8190abb1c293fb84329a |
completed | May 6, 2026, 12:32 p.m. |
Created at: May 3, 2026, 4:13 p.m.