Triple
T19530613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gayageum |
E488642
|
entity |
| Predicate | orientationWhenPlayed |
P135190
|
FINISHED |
| Object | horizontal |
—
|
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: horizontal | Statement: [Gayageum, orientationWhenPlayed, horizontal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orientationWhenPlayed Context triple: [Gayageum, orientationWhenPlayed, horizontal]
-
A.
orientationType
Indicates the specific kind or category of orientation relationship that exists between entities (such as spatial, directional, or alignment-based orientation).
-
B.
locationOrientation
chosen
Indicates how one entity is spatially oriented or positioned relative to a specific location or reference point.
-
C.
sessionOrientation
Indicates the directional or spatial alignment relationship established between entities within a session or interaction context.
-
D.
orientationInducedBy
Indicates that the orientation of one entity is determined or caused by the orientation or configuration of another entity.
-
E.
styleOrientation
Indicates the general stylistic direction or aesthetic approach that characterizes how something is designed, presented, or expressed.
- 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6363ec6cc8190b9e9ac0196b288f9 |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.