Triple
T37468434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gun (video game) |
E931090
|
entity |
| Predicate | hasHorseRiding |
P194887
|
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: [Gun (video game), hasHorseRiding, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHorseRiding Context triple: [Gun (video game), hasHorseRiding, yes]
-
A.
hasAnimalRide
chosen
Indicates that one entity provides or offers an animal as a means of transportation or ride to another entity.
-
B.
usesHorseType
Indicates that one entity employs, relies on, or operates using a specific type or category of horse.
-
C.
hasRidingAssociation
Indicates an association where one entity is related to another through the act or context of riding (e.g., serving as rider, mount, or riding partner).
-
D.
hasEquestrianFacility
Indicates that a place or property includes facilities specifically designed for horse-related activities, such as riding, training, or boarding.
-
E.
horseRequirement
Indicates that one entity requires, depends on, or mandates the presence or use of a horse in relation to another entity or activity.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: May 3, 2026, 4:17 p.m.