Triple
T9072121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAPRR |
E217392
|
entity |
| Predicate | associatedUNLocodeCountryCode |
P3519
|
FINISHED |
| Object | CA |
—
|
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: CA | Statement: [CAPRR, associatedUNLocodeCountryCode, CA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedUNLocodeCountryCode Context triple: [CAPRR, associatedUNLocodeCountryCode, CA]
-
A.
associatedCountryCode
Indicates that there is a relationship linking something to the country identified by the given country code.
-
B.
hasUNLocode
Indicates that an entity is associated with a specific UN/LOCODE, identifying its location in the United Nations location code system.
-
C.
ISOCode
Indicates that an entity is associated with a specific standardized code defined by the International Organization for Standardization (ISO).
-
D.
UNLOCODECountryCode
chosen
Indicates that an entity is associated with a specific country code as defined by the UN/LOCODE standard.
-
E.
associatedCountry
Indicates that there is a relevant connection or linkage between an entity and a specific country, such as origin, operation, or affiliation.
- 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_69ca83d6c14c8190bc056d927f00a2a2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc955ffa04819086be5763133c5067 |
completed | April 1, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:12 p.m.