Triple
T5261728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BRICKYARD |
E118839
|
entity |
| Predicate | callSignFormat |
P54893
|
FINISHED |
| Object | spoken word followed by flight number |
—
|
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: spoken word followed by flight number | Statement: [BRICKYARD, callSignFormat, spoken word followed by flight number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callSignFormat Context triple: [BRICKYARD, callSignFormat, spoken word followed by flight number]
-
A.
callSignSpokenForm
chosen
Indicates the spoken or verbalized form used to refer to a particular call sign.
-
B.
callSignType
Indicates the classification or category of a call sign associated with an entity or communication.
-
C.
callSignForOffice
Indicates that a particular call sign is assigned to or used for a specific office or official position.
-
D.
callSignForPerson
Indicates that a particular call sign is assigned to or used by a specific person.
-
E.
callSignScope
Indicates that a particular call sign is valid, applicable, or in effect only within a specified scope, context, or jurisdiction.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bd0c5f48190a1be89314c59f96b |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.