Triple
T14438728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscri Fortified Church |
E358033
|
entity |
| Predicate | locatedInVillageKnownFor |
P75597
|
FINISHED |
| Object | traditional rural heritage |
—
|
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: traditional rural heritage | Statement: [Viscri Fortified Church, locatedInVillageKnownFor, traditional rural heritage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInVillageKnownFor Context triple: [Viscri Fortified Church, locatedInVillageKnownFor, traditional rural heritage]
-
A.
isInVillage
Indicates that one entity is located within or belongs to the area defined as a village in relation to another entity.
-
B.
hasVillage
Indicates that an entity possesses, contains, or is associated with a village.
-
C.
hasNearbyTraditionalVillage
chosen
Indicates that an entity is located close to or in the vicinity of a traditional village.
-
D.
valleyKnownFor
Indicates that a particular valley is widely recognized or notable for a specific feature, product, activity, or characteristic.
-
E.
hasLargestVillage
Indicates that one entity possesses or contains the village that is largest in size or population within a specified context or set.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de914a45ec81909ab8ccf302047d7f |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.