Triple
T15838269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ETSI EN 302 307 |
E384036
|
entity |
| Predicate | definesPilotStructure |
P86856
|
FINISHED |
| Object | pilot symbols |
—
|
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: pilot symbols | Statement: [ETSI EN 302 307, definesPilotStructure, pilot symbols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesPilotStructure Context triple: [ETSI EN 302 307, definesPilotStructure, pilot symbols]
-
A.
definesStructure
chosen
Indicates that one entity specifies or determines the organizational form, composition, or arrangement of another entity.
-
B.
pilotDirector
Indicates that one entity serves as the director of the pilot episode or initial installment of another entity (such as a series or project).
-
C.
hasPilot
Indicates that an entity is operated or controlled by a specific pilot.
-
D.
hasPilotType
Indicates that an entity has or is associated with a specific type or category of pilot.
-
E.
isPilotOf
Indicates that one entity serves as the pilot who operates or controls another entity, typically a vehicle or aircraft.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e3d48c8190ad0d0af89d062101 |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.