Triple
T15935710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VCCJ |
E386435
|
entity |
| Predicate | prefixRepresents |
P7142
|
FINISHED |
| Object | Sri Lanka in ICAO airport codes |
—
|
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: Sri Lanka in ICAO airport codes | Statement: [VCCJ, prefixRepresents, Sri Lanka in ICAO airport codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prefixRepresents Context triple: [VCCJ, prefixRepresents, Sri Lanka in ICAO airport codes]
-
A.
namePrefix
Indicates that one entity is a prefix or leading part of another entity’s name.
-
B.
firstPartRepresents
Indicates that the initial segment or portion of something stands for, symbolizes, or denotes a larger whole or specific concept.
-
C.
representsBefore
Indicates that one entity occurs, exists, or is positioned earlier in time or sequence than another entity.
-
D.
registrationPrefix
chosen
Indicates that an entity has a specific registration prefix code assigned to it as part of its official registration or identification.
-
E.
namespacePrefix
Indicates the abbreviated prefix string associated with a particular namespace URI in a naming or identifier system.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.