Triple
T33197147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intha people |
E849796
|
entity |
| Predicate | rowingTechnique |
P81627
|
FINISHED |
| Object | leg-rowing |
—
|
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: leg-rowing | Statement: [Intha people, rowingTechnique, leg-rowing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rowingTechnique Context triple: [Intha people, rowingTechnique, leg-rowing]
-
A.
rowingStyle
chosen
Indicates the specific technique or manner in which an entity performs the action of rowing.
-
B.
martialArt
Indicates that one entity practices, performs, or is associated with a specific martial art style or discipline in relation to another entity.
-
C.
demonstratedTechniqueFocus
Indicates that an entity has shown or highlighted a particular technique as the main focus of its demonstration.
-
D.
drivingTechnique
Indicates a method or style used by a driver to control and maneuver a vehicle.
-
E.
techniqueRequired
Indicates that performing one entity (such as an action, process, or task) necessitates the use of a specific technique associated with the other entity.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:29 a.m.