Triple
T11711972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PlayStation Move |
E278393
|
entity |
| Predicate | orbFunction |
P23285
|
FINISHED |
| Object | position tracking |
—
|
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: position tracking | Statement: [PlayStation Move, orbFunction, position tracking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbFunction Context triple: [PlayStation Move, orbFunction, position tracking]
-
A.
coordinateFunction
Indicates a functional relationship that maps or translates one set of coordinates to another within a defined space or system.
-
B.
coordinatesFunction
Indicates a relationship where one entity organizes, schedules, or manages the execution of a function or activity involving other entities.
-
C.
associatedFunction
chosen
Indicates that one entity has a related or linked function that is conceptually or operationally connected to it.
-
D.
assignedFunction
Indicates that a specific role, duty, or function has been formally allocated to an entity.
-
E.
coordinationFunction
Indicates a relationship where one entity organizes, aligns, or manages the activities or interactions of other entities to ensure they work together effectively.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4be10088190854699385d1f6a95 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7d483081909c2a101087515d74 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.