Triple
T35464414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IX Region |
E1025024
|
entity |
| Predicate | formerNumericalDesignation |
P81719
|
FINISHED |
| Object | Region IX |
—
|
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: Region IX | Statement: [IX Region, formerNumericalDesignation, Region IX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerNumericalDesignation Context triple: [IX Region, formerNumericalDesignation, Region IX]
-
A.
formerDesignation
Indicates that an entity previously held a particular title, role, or designation that it no longer holds.
-
B.
hasDesignationNumber
Indicates that an entity is associated with a specific official designation or identification number.
-
C.
previouslyUsedNumberDesignationsUntil
chosen
Indicates that certain number designations were used for an entity up until a specified point in time, after which they were no longer in use.
-
D.
alternateDesignation
Indicates that one entity serves as an alternative name, label, or identifier for another entity.
-
E.
typicalDesignation
Indicates that one entity is the usual or commonly used designation (name, label, or title) 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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a005d878aec81908e1177914a8fb610 |
completed | May 10, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_6a005c382f8881908ff33ebb7f88c430 |
completed | May 10, 2026, 10:21 a.m. |
Created at: May 3, 2026, 4:04 p.m.