Triple
T22071992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dayak lute |
E545429
|
entity |
| Predicate | soundHolePosition |
P71748
|
FINISHED |
| Object | front of the body |
—
|
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: front of the body | Statement: [Dayak lute, soundHolePosition, front of the body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soundHolePosition Context triple: [Dayak lute, soundHolePosition, front of the body]
-
A.
speakerPosition
Indicates the spatial or contextual location of a speaker relative to other entities or a reference frame during an utterance or event.
-
B.
hasSoundHole
chosen
Indicates that one entity possesses or features a sound hole as a characteristic or component.
-
C.
earPosition
Indicates the spatial orientation or placement of an ear relative to a reference point or object.
-
D.
hornPosition
Indicates the relative placement or orientation of a horn with respect to a reference point or object.
-
E.
headsetHapticsLocation
Indicates the specific physical area or position on a headset where haptic feedback is applied or experienced.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12888dcc08190b18d3d44d09ab943 |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:28 p.m.