Triple
T21277670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orlando |
E524431
|
entity |
| Predicate | blows |
P143482
|
FINISHED |
| Object | oliphant horn |
—
|
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: oliphant horn | Statement: [Orlando, blows, oliphant horn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blows Context triple: [Orlando, blows, oliphant horn]
-
A.
blowsAcross
Indicates that something (typically wind, air, or a current) moves across or over another entity or area, passing from one side or region to another.
-
B.
blowsOver
Indicates that one entity is toppled or knocked down by the force or movement of another entity.
-
C.
breathes
Indicates that one entity inhales and exhales air or another gas as part of a respiratory process.
-
D.
backblast
Indicates the backward-directed blast or pressure effect produced as a result of an explosive discharge or propulsion event.
-
E.
by
Indicates that an action is performed, caused, or authored through the agency, means, or proximity of a specified entity.
- 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_69e0b516293c819089458ea2ec85f85e |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736583c08819087a4726538e703e2 |
completed | April 21, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69e5f6161dac8190b06009cd180e3ff7 |
completed | April 20, 2026, 9:47 a.m. |
| PDg | Predicate description generation | batch_69e5f9943ed881909ef49045c5bcf6df |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 4:02 p.m.