Triple
T35351065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phanom Rung Historical Park |
E1020879
|
entity |
| Predicate | hasLintels |
P197714
|
FINISHED |
| Object | Khmer carved lintels |
—
|
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: Khmer carved lintels | Statement: [Phanom Rung Historical Park, hasLintels, Khmer carved lintels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLintels Context triple: [Phanom Rung Historical Park, hasLintels, Khmer carved lintels]
-
A.
hasCantilever
Indicates that one entity possesses or incorporates a cantilever structure in relation to another entity or context.
-
B.
hasLiningMaterial
Indicates that one entity uses or contains another entity as the material forming its inner lining.
-
C.
hasBalustrades
Indicates that one entity features or is equipped with balustrades as part of its structure or design.
-
D.
hasMezzanine
Indicates that one entity includes or is equipped with a mezzanine level in relation to another entity.
-
E.
hasPilotis
Indicates that a building or structure is elevated on pilotis (supporting columns or stilts), rather than resting directly on the ground.
- 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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fea2d0a4d08190aa06aeb902a02d5a |
completed | May 9, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fea24698348190b9b992a8e7cdbcd0 |
completed | May 9, 2026, 2:56 a.m. |
| PDg | Predicate description generation | batch_69fea2cfcd648190a15e5b90889095b1 |
completed | May 9, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:03 p.m.