Triple
T11067675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IPGP |
E261666
|
entity |
| Predicate | affiliation |
P10
|
FINISHED |
| Object | IRD |
E860378
|
NE 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: IRD | Statement: [IPGP, affiliation, IRD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IRD Context triple: [IPGP, affiliation, IRD]
-
A.
IRD
chosen
IRD is an organization that manages and operates the Coriolis data center, providing infrastructure and services for data processing and storage.
-
B.
IRD
IRD is New Zealand’s government tax authority responsible for collecting revenue, administering social support payments, and overseeing the country’s tax system.
-
C.
IR
IR is the IATA airline designator assigned to Iran Air, the national flag carrier of Iran.
-
D.
IR
IR is the branding abbreviation used for InterRegio, a category of medium- to long-distance passenger trains operating in several European countries.
-
E.
IR
IR is the ISO 3166-1 alpha-2 country code for Iran, a large Middle Eastern nation known for its ancient Persian heritage and significant geopolitical influence.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79920428c81908db824ab54e08e8d |
completed | April 9, 2026, 12:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3c8a4cdb8819080765d746f477089 |
completed | April 18, 2026, 6:08 p.m. |
Created at: April 8, 2026, 9:26 p.m.