Triple
T7695488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alabama Territory |
E174357
|
entity |
| Predicate | ISO3166Status |
P78768
|
FINISHED |
| Object | no current ISO 3166 code (historical entity) |
—
|
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: no current ISO 3166 code (historical entity) | Statement: [Alabama Territory, ISO3166Status, no current ISO 3166 code (historical entity)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO3166Status Context triple: [Alabama Territory, ISO3166Status, no current ISO 3166 code (historical entity)]
-
A.
ISO3166Relation
Indicates a relationship that associates an entity with its corresponding ISO 3166 country or region code as defined by the international standard.
-
B.
ISO3166Basis
Indicates that one standard, classification, or designation is defined or derived based on the ISO 3166 country code system.
-
C.
ISO3166-2DifferentFrom
Indicates that two ISO 3166-2 subdivision codes are explicitly distinct and should not be considered equivalent or interchangeable.
-
D.
hasISO3166-1NumericCode
Indicates that an entity is associated with a specific ISO 3166-1 numeric country code.
-
E.
ISO3166codePredecessorOf
Indicates that one ISO 3166 country code served as the predecessor or was replaced by another ISO 3166 country code in the standard’s historical sequence.
- F. None of above. chosen
Provenance (4 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_69c6995966348190939e6c37ba272c06 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c706d1f0208190bc5b695aa5736244 |
completed | March 27, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69c70163dea88190ae729df50e63dfd7 |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c706d0c1708190a3e74523997814b8 |
completed | March 27, 2026, 10:38 p.m. |
Created at: March 27, 2026, 4:02 p.m.