Triple
T35907144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Far Cry series |
E1038501
|
entity |
| Predicate | hasMapEditor |
P204001
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Far Cry series, hasMapEditor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMapEditor Context triple: [Far Cry series, hasMapEditor, true]
-
A.
hasMultiplayerMapEditor
Indicates that the subject includes a map editor feature that can be used by multiple players simultaneously.
-
B.
hasMapframe
Indicates that an entity is associated with an embedded, interactive map frame representation of its geographic location or area.
-
C.
hasMaps
Indicates that one entity possesses, includes, or provides access to one or more maps associated with another entity.
-
D.
hasMusicEditor
Indicates that one entity serves as the music editor responsible for selecting, editing, or supervising the music used in another entity (such as a film, show, or production).
-
E.
hasMapRegion
Indicates that an entity is associated with, or belongs to, a specific geographic or logical map region.
- 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0308a4591081909018e2ba5d70096e |
completed | May 12, 2026, 11:01 a.m. |
| PD | Predicate disambiguation | batch_6a03079299708190a2ecaf14d3f06f48 |
completed | May 12, 2026, 10:57 a.m. |
| PDg | Predicate description generation | batch_6a0308a3b03c8190b7fc9553afe06cb5 |
completed | May 12, 2026, 11:01 a.m. |
Created at: May 3, 2026, 4:07 p.m.