Triple
T13991752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tofol |
E336593
|
entity |
| Predicate | hasISO3166-2CodeOfState |
P42695
|
FINISHED |
| Object | FM-KSA |
—
|
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: FM-KSA | Statement: [Tofol, hasISO3166-2CodeOfState, FM-KSA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasISO3166-2CodeOfState Context triple: [Tofol, hasISO3166-2CodeOfState, FM-KSA]
-
A.
ISO3166-2RegionCode
chosen
Indicates the standardized ISO 3166-2 code that specifies the particular primary administrative subdivision (such as a state, province, or region) to which an entity belongs.
-
B.
stateSubdivisionCode
Indicates the standardized code that identifies a specific subdivision (such as a state, province, or region) within a larger country or territory.
-
C.
hasStateSubdivisionName
Indicates that an entity has a specific name for one of its internal state-level subdivisions.
-
D.
associatedSubdivisionISO3166-1Alpha2
Indicates that a subdivision (such as a state or province) is associated with a specific country identified by its ISO 3166-1 alpha-2 code.
-
E.
USStateSubdivision
Indicates that one entity is an administrative subdivision (such as a county, parish, or borough) within a U.S. state represented by the other 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2eb3b5d881909f15a1e08bb202f3 |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:19 p.m.