Triple
T36581319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | black-billed streamertail |
E902401
|
entity |
| Predicate | flightSound |
P161145
|
FINISHED |
| Object | wing-produced whirring or buzzing |
—
|
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: wing-produced whirring or buzzing | Statement: [black-billed streamertail, flightSound, wing-produced whirring or buzzing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightSound Context triple: [black-billed streamertail, flightSound, wing-produced whirring or buzzing]
-
A.
wingSound
chosen
Indicates that an entity produces or is associated with the sound generated by wings in motion.
-
B.
flightRecord
Indicates a record of a specific flight event or journey, capturing details about its occurrence and characteristics.
-
C.
flightAbility
Indicates the capability or potential of an entity to fly or engage in powered or unpowered aerial movement.
-
D.
natureOfFlight
Indicates the general type or characteristics of a flight, such as its purpose, category, or operational nature.
-
E.
flightMechanic
Indicates that one entity serves as a mechanic responsible for maintaining or repairing the aircraft associated with another 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.