Triple
T35907106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Far Cry series |
E1038501
|
entity |
| Predicate | latestMainlineRelease |
P3698
|
FINISHED |
| Object | Far Cry 6 |
—
|
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: Far Cry 6 | Statement: [Far Cry series, latestMainlineRelease, Far Cry 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: latestMainlineRelease Context triple: [Far Cry series, latestMainlineRelease, Far Cry 6]
-
A.
latestMinorVersion
Indicates that one version is the most recent minor (non-major) update within the series of versions derived from another version.
-
B.
latestReleaseBranch
Indicates that a branch is designated as the most recent official release branch in a version control or release management system.
-
C.
latestVersion
chosen
Indicates that one entity is the most recent or up-to-date version of another entity within a sequence or set of versions.
-
D.
latestMajorVersionNumber
Indicates the relationship that specifies the most recent major version number associated with an entity.
-
E.
latestCoreVersion
Indicates that one entity specifies or identifies the most recent or up-to-date core version associated with another entity.
- 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa6fd79c8190b1a70068ace78068 |
completed | May 3, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:07 p.m.