Triple
T14001834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phonsavan |
E336842
|
entity |
| Predicate | hasNearbyHeritageType |
P55205
|
FINISHED |
| Object | archaeological landscape |
—
|
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: archaeological landscape | Statement: [Phonsavan, hasNearbyHeritageType, archaeological landscape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyHeritageType Context triple: [Phonsavan, hasNearbyHeritageType, archaeological landscape]
-
A.
hasNearbyHistoricArea
Indicates that one entity is located close to another entity that is designated as a historic area.
-
B.
heritageSiteTypeNearby
chosen
Indicates that a particular type of heritage site is located in close proximity to the referenced entity.
-
C.
hasNearbyPilgrimageSite
Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
-
D.
hasAdjacentHistoricSite
Indicates that one place is directly next to or very near another place that is recognized as a historic site.
-
E.
hasNearbyCulturalDistrict
Indicates that an entity is located close to a designated cultural district or area with concentrated cultural activities.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ed06a50819093ddc64f55050689 |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:19 p.m.