Triple
T19379412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palanquin-Bearers |
E484756
|
entity |
| Predicate | meterFeature |
P4875
|
FINISHED |
| Object | strong rhythmic pattern suggesting movement |
—
|
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: strong rhythmic pattern suggesting movement | Statement: [Palanquin-Bearers, meterFeature, strong rhythmic pattern suggesting movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meterFeature Context triple: [Palanquin-Bearers, meterFeature, strong rhythmic pattern suggesting movement]
-
A.
meter
Indicates a measurement relationship where one entity quantifies the length, distance, or extent of another in meters.
-
B.
hasMeter
chosen
Indicates that one entity possesses, uses, or is associated with a specific meter (a measuring device or metrical pattern).
-
C.
measuredProperty
Indicates that the subject is a measurement that quantifies or assesses the specified property of an entity.
-
D.
hasFloorFeature
Indicates that a floor possesses or includes a specific feature or characteristic.
-
E.
meterSystem
Indicates that one entity uses, is measured in, or is associated with a particular system of meters or measurement units.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a5e8e7081908bed3eee1eef4de2 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.