Triple
T19379399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palanquin-Bearers |
E484756
|
entity |
| Predicate | comparesMovementTo |
P135744
|
FINISHED |
| Object | a bird on the wing |
—
|
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: a bird on the wing | Statement: [Palanquin-Bearers, comparesMovementTo, a bird on the wing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparesMovementTo Context triple: [Palanquin-Bearers, comparesMovementTo, a bird on the wing]
-
A.
usesMovement
Indicates that an entity performs or involves some form of movement as part of its action or behavior.
-
B.
describesMovement
Indicates that an entity undergoes or performs a change of position or location, capturing how it moves from one place or state to another.
-
C.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
D.
basedOnMovement
Indicates that something is determined, derived, or decided according to the movement or motion of an entity.
-
E.
hasRelationToOtherMovements
Indicates that something is connected, associated, or otherwise related to other movements in a meaningful way.
- 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_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. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:35 p.m.