Triple
T37303941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arx Libertatis |
E926028
|
entity |
| Predicate | supportsOriginalGameData |
P196625
|
FINISHED |
| Object | Arx Fatalis |
E270958
|
NE 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: Arx Fatalis | Statement: [Arx Libertatis, supportsOriginalGameData, Arx Fatalis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsOriginalGameData Context triple: [Arx Libertatis, supportsOriginalGameData, Arx Fatalis]
-
A.
originGame
Indicates the game from which an entity, such as a character, item, or concept, originally comes.
-
B.
requiresOriginalDataFilesFrom
chosen
Indicates that one entity depends on accessing the other entity’s original data files in order to function or be completed.
-
C.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
-
D.
supportsGames
Indicates that an entity is capable of running, handling, or being compatible with one or more games.
-
E.
hasOriginalScoreFor
Indicates that one entity is the original musical score specifically composed for another entity, such as a film, show, or performance.
- F. None of above.
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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40afcc8f3c819086297e0621e54f97 |
completed | June 28, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.