Triple
T32924792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baháʼí Era |
E842236
|
entity |
| Predicate | startCountryHistorical |
P1823
|
FINISHED |
| Object | Persia |
—
|
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: Persia | Statement: [Baháʼí Era, startCountryHistorical, Persia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startCountryHistorical Context triple: [Baháʼí Era, startCountryHistorical, Persia]
-
A.
countryInThePast
Indicates that an entity was recognized as a country during some period in the past, but is not necessarily a country in the present.
-
B.
countryOfHistoricRole
Indicates the country in which an entity held a significant historical role or carried out historically notable activities.
-
C.
countryHistoryTopic
Indicates that a subject is associated with a historical topic, theme, or aspect specifically related to a particular country.
-
D.
chronologyWithinCountry
Indicates that one event or time period occurs within the temporal sequence of another, specifically in the context of a single country.
-
E.
historicalOrigin
chosen
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff90b673248190b4dda9e005642d17 |
completed | May 9, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69ff8d5bee1081909274052945e98a6f |
completed | May 9, 2026, 7:39 p.m. |
Created at: May 1, 2026, 1:20 a.m.