Triple
T35351048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phanom Rung Historical Park |
E1020879
|
entity |
| Predicate | mainSanctuaryCompleted |
P65786
|
FINISHED |
| Object | 12th century |
—
|
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: 12th century | Statement: [Phanom Rung Historical Park, mainSanctuaryCompleted, 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainSanctuaryCompleted Context triple: [Phanom Rung Historical Park, mainSanctuaryCompleted, 12th century]
-
A.
hasSanctuary
Indicates that one entity provides or serves as a place of refuge, protection, or safe haven for another entity.
-
B.
hasOldSanctuary
Indicates that an entity possesses or is associated with an old or former sanctuary.
-
C.
hasMainSanctum
chosen
Indicates that an entity possesses a primary or central sacred space used for core religious or spiritual activities.
-
D.
builtSanctuaryAt
Indicates that an entity constructed or established a sanctuary at a specific location.
-
E.
hadSanctuaryOf
Indicates that an entity possessed or hosted a sanctuary dedicated 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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.