Triple
T19530614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gayageum |
E488642
|
entity |
| Predicate | performancePosture |
P42040
|
FINISHED |
| Object | seated |
—
|
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: seated | Statement: [Gayageum, performancePosture, seated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performancePosture Context triple: [Gayageum, performancePosture, seated]
-
A.
describesPosture
chosen
Indicates that one entity specifies or characterizes the bodily position or stance (posture) of another entity.
-
B.
proceduralPosture
Indicates the current stage or status of a legal case within the judicial or administrative process at the time it is being considered or described.
-
C.
performanceWith
Indicates a relationship where two or more entities participate together in the same performance or staged presentation.
-
D.
performanceModel
Indicates a relationship where one entity serves as a performance model that represents, predicts, or characterizes the performance behavior of another entity.
-
E.
performanceArea
Indicates the area or space in which a performance, show, or event takes place.
- 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.