Triple
T35257074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phimai Historical Park |
E1018259
|
entity |
| Predicate | hasCentralPrang |
P191836
|
FINISHED |
| Object | main sandstone tower |
—
|
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: main sandstone tower | Statement: [Phimai Historical Park, hasCentralPrang, main sandstone tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralPrang Context triple: [Phimai Historical Park, hasCentralPrang, main sandstone tower]
-
A.
hasCentralAct
Indicates that an entity includes or is characterized by a primary or most important action, event, or operation at its core.
-
B.
hasCentralCharge
Indicates that an entity is associated with, or characterized by, a specific central charge value in a given theoretical or physical framework.
-
C.
hasCentralSection
Indicates that an entity possesses a distinct middle or central part within its overall structure or composition.
-
D.
hasCentralPerformance
Indicates that an entity includes or features a primary, focal performance at its core.
-
E.
hasCentralClaim
Indicates that one entity presents or embodies the main assertion, thesis, or primary point made by another entity.
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
| PDg | Predicate description generation | batch_69fcec5e560481909cd710b88897e833 |
completed | May 7, 2026, 7:47 p.m. |
Created at: May 3, 2026, 4:02 p.m.