Triple
T36754078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rostam |
E907995
|
entity |
| Predicate | transportCountryCode |
P37933
|
FINISHED |
| Object | IRN |
—
|
NE NERFINISHED |
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: IRN | Statement: [Rostam, transportCountryCode, IRN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportCountryCode Context triple: [Rostam, transportCountryCode, IRN]
-
A.
componentCountryCode
Indicates that one entity specifies the country code associated with a component of another entity.
-
B.
sendingCountry
chosen
Indicates the country from which something (such as a person, object, or communication) is sent or dispatched.
-
C.
postalCountry
Indicates the country associated with an entity’s postal or mailing address.
-
D.
bearerCountry
Indicates the country that serves as the issuer or origin nation associated with a given bearer (such as a document, instrument, or entity).
-
E.
continentCode
Indicates the standardized code assigned to the continent with which an entity is associated.
- 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_69f76e779bec8190be0e1f87a131e0f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffa5f31c8881908c26e2aa52df6ece |
completed | May 9, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69ffa42aee408190ad1a5f285688b338 |
completed | May 9, 2026, 9:16 p.m. |
Created at: May 3, 2026, 4:12 p.m.