Triple
T37504010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Far Reach |
E932043
|
entity |
| Predicate | objectMechanic |
P187880
|
FINISHED |
| Object | pulls target toward user |
—
|
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: pulls target toward user | Statement: [Far Reach, objectMechanic, pulls target toward user]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectMechanic Context triple: [Far Reach, objectMechanic, pulls target toward user]
-
A.
mechanicalFunction
Indicates that one entity serves as the mechanical role, operation, or function performed by another entity or system.
-
B.
mecanismo
Indicates a mechanism or means by which one entity brings about, enables, or explains the effect, function, or outcome in another entity.
-
C.
interactionMechanism
Indicates the process or means by which one entity affects, influences, or interacts with another.
-
D.
mechanismBy
Indicates that one entity occurs, is produced, or is brought about by means of another entity, which serves as its mechanism or causal process.
-
E.
keyMechanic
chosen
Indicates that the referenced element functions as a central or essential gameplay mechanic within a system or experience.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.