Triple
T4314044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthophorini |
E94143
|
entity |
| Predicate | flightPeriod |
P56404
|
FINISHED |
| Object | day-active |
—
|
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: day-active | Statement: [Anthophorini, flightPeriod, day-active]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightPeriod Context triple: [Anthophorini, flightPeriod, day-active]
-
A.
flightHours
Indicates the number of hours an entity has spent in flight or operating in the air.
-
B.
flightDuration
Indicates the length of time that a specific flight takes from departure to arrival.
-
C.
flightPhase
Indicates the specific stage or phase of an aircraft’s operation within a flight (e.g., taxi, takeoff, climb, cruise, descent, landing).
-
D.
operatorDuringRecordFlight
Indicates that an operator is responsible for or engaged in operating a system or vehicle during the time a particular flight is being recorded.
-
E.
flightRegime
Indicates the operational conditions or phase of flight under which an aircraft or aerospace vehicle is functioning (e.g., speed, altitude, and atmospheric regime).
- 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_69b3451886588190a3dd1305ea7c58dc |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b350f319c08190bb40a9fc5933728d |
completed | March 12, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69b34f4a07b08190a06ada0d9cbb14fb |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b35034cd248190bae09e9d090e13ec |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:12 p.m.