Triple
T33039558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomb Raider: Chronicles |
E845420
|
entity |
| Predicate | hasLevelEditor |
P171874
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tomb Raider: Chronicles, hasLevelEditor, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLevelEditor Context triple: [Tomb Raider: Chronicles, hasLevelEditor, yes]
-
A.
levelEditor
chosen
Indicates that an entity functions as or is associated with a tool or environment used to create, modify, or arrange levels or stages within a game or application.
-
B.
hasLevelDesign
Indicates that one entity possesses, is associated with, or is defined by a particular level design created or specified by another entity.
-
C.
hasMultiplayerMapEditor
Indicates that the subject includes a map editor feature that can be used by multiple players simultaneously.
-
D.
hasEditorScripting
Indicates that an entity provides or supports scripting capabilities specifically for editing or editor-related functionality.
-
E.
architectureLevel
Indicates the relative layer or tier an entity occupies within an architectural structure or system design.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: May 1, 2026, 1:24 a.m.