Triple
T24955903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | koto |
E624470
|
entity |
| Predicate | performancePosition |
P86740
|
FINISHED |
| Object | placed horizontally |
—
|
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: placed horizontally | Statement: [koto, performancePosition, placed horizontally]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performancePosition Context triple: [koto, performancePosition, placed horizontally]
-
A.
positionInPerformance
chosen
Indicates the specific ordering or placement of an entity within a performance or sequence of performed elements.
-
B.
performanceWith
Indicates a relationship where two or more entities participate together in the same performance or staged presentation.
-
C.
performerPosition
Indicates the spatial or role-based placement of a performer relative to a performance context or other participants.
-
D.
performanceArea
Indicates the area or space in which a performance, show, or event takes place.
-
E.
performanceOutcome
Indicates the result, effect, or consequence produced by a particular performance or action.
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 5:57 a.m.