Triple
T29416924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baldur's Gate II: Shadows of Amn |
E746049
|
entity |
| Predicate | enhancedEditionDeveloper |
P166760
|
FINISHED |
| Object | Beamdog |
—
|
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: Beamdog | Statement: [Baldur's Gate II: Shadows of Amn, enhancedEditionDeveloper, Beamdog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enhancedEditionDeveloper Context triple: [Baldur's Gate II: Shadows of Amn, enhancedEditionDeveloper, Beamdog]
-
A.
laterDeveloper
Indicates that one developer’s work, role, or involvement occurs after another developer in time.
-
B.
remakeDeveloper
chosen
Indicates that a developer is responsible for creating a new version or adaptation of an existing work (such as a game, app, or software).
-
C.
enhancedBy
Indicates that one entity’s value, effectiveness, or impact is increased or improved as a result of another entity.
-
D.
platformDeveloper
Indicates that one entity is the developer or creator responsible for building or maintaining the other entity as a platform.
-
E.
developerOfContainingGame
Indicates that an entity is the developer responsible for creating the game that contains the referenced element or component.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a666e5c8190ae53ea01f2195ac1 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:02 p.m.