Triple
T7949363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LIMC |
E184574
|
entity |
| Predicate | icaoCountryPrefix |
P34409
|
FINISHED |
| Object | LI |
—
|
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: LI | Statement: [LIMC, icaoCountryPrefix, LI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: icaoCountryPrefix Context triple: [LIMC, icaoCountryPrefix, LI]
-
A.
icaoRegionPrefix
chosen
Indicates the regional ICAO prefix that designates the geographic or administrative region associated with an aviation-related entity.
-
B.
UICCountryCode
Indicates that an entity is associated with a specific country identified by its UIC (International Union of Railways) country code.
-
C.
ICCCode
Indicates that an entity is associated with a specific International Criminal Court (ICC) code, identifying its classification or legal reference under ICC standards.
-
D.
callingCode
Indicates the telephone country or area code associated with an entity for making phone calls.
-
E.
FIPSCountryCode
Indicates that an entity is associated with a specific country as identified by its FIPS (Federal Information Processing Standards) country code.
- 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_69ca8292cba881908a64427b938dac47 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b2d09a4819097aa49e29a5426ec |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae9361bc48190886b7681e563d46b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:10 p.m.