Triple
T26743424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chiang Puak Gate |
E674326
|
entity |
| Predicate | hasCityGateRole |
P74346
|
FINISHED |
| Object | northern entrance to Chiang Mai Old City |
—
|
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: northern entrance to Chiang Mai Old City | Statement: [Chiang Puak Gate, hasCityGateRole, northern entrance to Chiang Mai Old City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityGateRole Context triple: [Chiang Puak Gate, hasCityGateRole, northern entrance to Chiang Mai Old City]
-
A.
hasCityGateFunction
chosen
Indicates that something serves the role or function of a city gate, such as controlling access, passage, or boundary between a city and its surroundings.
-
B.
hasCityGateStatus
Indicates the status or condition of a city gate in relation to a given entity.
-
C.
hasCityGateRemains
Indicates that a location contains surviving structural remains of a former city gate.
-
D.
hasGate
Indicates that one entity possesses, includes, or is equipped with a gate as part of its structure or configuration.
-
E.
hasGatekeeper
Indicates that one entity serves as a controlling or mediating gatekeeper for access to 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 3:50 a.m.