Triple
T38497999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sai Noi District |
E919746
|
entity |
| Predicate | geocodeType |
P190965
|
FINISHED |
| Object | Geocode |
—
|
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: Geocode | Statement: [Sai Noi District, geocodeType, Geocode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geocodeType Context triple: [Sai Noi District, geocodeType, Geocode]
-
A.
hasGeocode
Indicates that an entity is associated with a specific geographic coordinate or coded location reference.
-
B.
gridReferenceType
Indicates the specific system or format used to express a location’s position within a spatial grid.
-
C.
mappingType
Indicates the specific kind or category of correspondence established between two related elements or representations.
-
D.
isGeographicCode
Indicates that one entity functions as a geographic code that identifies or represents the location of another entity.
-
E.
hasGeographicType
Indicates that an entity is associated with or classified by a specific type or category of geographic feature or area.
- 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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd34596288190b8e34a7a20b4c0db |
completed | May 7, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd31227708190a7df213597e66ca8 |
completed | May 7, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:31 p.m.