Triple
T33431106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PH-LAN |
E856132
|
entity |
| Predicate | regionClassificationSystem |
P6736
|
FINISHED |
| Object | ISO 3166 |
—
|
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: ISO 3166 | Statement: [PH-LAN, regionClassificationSystem, ISO 3166]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionClassificationSystem Context triple: [PH-LAN, regionClassificationSystem, ISO 3166]
-
A.
regionClassification
Indicates how a given area or location is categorized into a specific region based on defined criteria or boundaries.
-
B.
regionallyClassifiedAs
Indicates that something is assigned to or identified with a specific geographic or regional category.
-
C.
classificationSystem
chosen
Indicates a relationship where an entity is organized or categorized according to a particular classification scheme or taxonomy.
-
D.
regionTypeOfPlace
Indicates that a place belongs to or is categorized under a specific type of geographic or administrative region.
-
E.
classificationSystemBasedOn
Indicates that one classification system is organized, defined, or derived using another classification system as its basis or reference framework.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff2fbae9b48190847eefa1c227d43e |
completed | May 9, 2026, 12:59 p.m. |
| PD | Predicate disambiguation | batch_69ff2f2218048190a32224a648182b5d |
completed | May 9, 2026, 12:57 p.m. |
Created at: May 1, 2026, 1:36 a.m.