Triple
T10189830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIU |
E238002
|
entity |
| Predicate | alpha2CompanionCode |
P2261
|
FINISHED |
| Object | NU |
—
|
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: NU | Statement: [NIU, alpha2CompanionCode, NU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alpha2CompanionCode Context triple: [NIU, alpha2CompanionCode, NU]
-
A.
alphabeticCode
Indicates that one entity is identified or represented by a specific alphabetic code assigned to it.
-
B.
alpha2Relation
Indicates a secondary or alternative relational link between entities, often representing a second-level or auxiliary association distinct from a primary (alpha1) relation.
-
C.
isTwoLetterCode
chosen
Indicates that something functions as a two-letter abbreviated code representing a larger name or concept.
-
D.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
E.
ISO3166-2RegionCode
Indicates the standardized ISO 3166-2 code that specifies the particular primary administrative subdivision (such as a state, province, or region) to which an entity belongs.
- 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_69ca84de1b208190bf17bb305b002605 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded7d6fdc81908052866495b6574f |
completed | April 2, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8477648190bc55c56aeec507d3 |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:12 p.m.