Triple
T11524674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AAR |
E273260
|
entity |
| Predicate | designatorCategory |
P99941
|
FINISHED |
| Object | three-letter ICAO code |
—
|
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: three-letter ICAO code | Statement: [AAR, designatorCategory, three-letter ICAO code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designatorCategory Context triple: [AAR, designatorCategory, three-letter ICAO code]
-
A.
designatorType
Indicates the specific role or category of a designator used to identify or reference an entity within a system or context.
-
B.
designationCategory
Indicates the classification or type of designation assigned to an entity within a broader designation system.
-
C.
designCategory
Indicates that one entity is classified under a particular design-related category or type.
-
D.
designationFor
Indicates that one entity serves as the official title, label, or role name assigned to another entity.
-
E.
designationComponent
Indicates that one entity functions as a component or constituent part of another entity’s designation or formal naming.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d87fd26648819083de19bcddf8ad69 |
completed | April 10, 2026, 4:42 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:37 p.m.