Triple
T22532985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishutan |
E557088
|
entity |
| Predicate | nationalityInEpic |
P15237
|
FINISHED |
| Object | Iranian |
—
|
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: Iranian | Statement: [Bishutan, nationalityInEpic, Iranian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalityInEpic Context triple: [Bishutan, nationalityInEpic, Iranian]
-
A.
nationalEpic
Indicates that one work is regarded as the principal epic narrative representing the history, culture, or identity of a nation.
-
B.
nationalityInStory
chosen
Indicates that a character or entity in a narrative is associated with a particular nationality within the context of that story.
-
C.
nationalityInHumanWorld
Indicates that one entity has the specified national affiliation or citizenship within the context of the human world.
-
D.
nationalityInMyth
Indicates that a mythological figure, character, or entity is associated with a particular nationality or cultural tradition within mythology.
-
E.
nationalityOfFictionalSetting
Indicates that a fictional setting is associated with, or belongs to, a particular nationality or country.
- 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ed88cf08190ae7e5b6bf9a80372 |
completed | April 29, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:51 p.m.