Triple
T33647755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DREAMJET |
E862006
|
entity |
| Predicate | hasCallsignRole |
P176146
|
FINISHED |
| Object | standardized spoken identifier for La Compagnie flights |
—
|
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: standardized spoken identifier for La Compagnie flights | Statement: [DREAMJET, hasCallsignRole, standardized spoken identifier for La Compagnie flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCallsignRole Context triple: [DREAMJET, hasCallsignRole, standardized spoken identifier for La Compagnie flights]
-
A.
hasCallsignPrefixRole
Indicates that an entity has a specific role associated with a given callsign prefix.
-
B.
hasCallSignOwner
Indicates that a particular call sign is owned or assigned to a specific entity.
-
C.
hasCallsignCompanion
Indicates that one entity serves as a companion or associated partner to another entity’s callsign.
-
D.
callsignOrDesignation
chosen
Indicates that one entity serves as the callsign or formal designation used to identify another entity in communication or operational contexts.
-
E.
hasCallsignSuffix
Indicates that an entity’s callsign includes a specific suffix component appended to its main identifier.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
Created at: May 1, 2026, 1:42 a.m.