Triple
T30682957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cretan lyra |
E781105
|
entity |
| Predicate | typicalBowingTechnique |
P207297
|
FINISHED |
| Object | short fast strokes |
—
|
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: short fast strokes | Statement: [Cretan lyra, typicalBowingTechnique, short fast strokes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBowingTechnique Context triple: [Cretan lyra, typicalBowingTechnique, short fast strokes]
-
A.
bowSection
Indicates a relationship where one entity is a specific section or part of the bow (such as on a stringed instrument or weapon) associated with another entity.
-
B.
bendingSubskill
Indicates a specific skill or technique that forms part of the broader ability to bend or flex something.
-
C.
hasBowType
Indicates that an entity possesses or is associated with a specific type or category of bow.
-
D.
typicalMudra
Indicates that one entity is the characteristic or commonly used mudra (hand gesture) associated with another entity, such as a deity, practice, or tradition.
-
E.
hasBowlingDirection
Indicates that one entity performs or directs a bowling action toward another entity or in a specified direction.
- F. None of above. chosen
Provenance (4 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 8:33 p.m.