Triple
T35573423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agoriani |
E1028005
|
entity |
| Predicate | mountainVillage |
P183416
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Agoriani, mountainVillage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountainVillage Context triple: [Agoriani, mountainVillage, true]
-
A.
locatedInHills
Indicates that something is situated within or among hilly terrain or a region characterized by hills.
-
B.
mountainAccess
Indicates that an entity has the ability, right, or means to reach, enter, or utilize a mountain or mountainous area.
-
C.
mountainFeature
Indicates that one entity is a notable physical or geographical feature associated with, located on, or forming part of a mountain.
-
D.
holyMountain
Indicates that a mountain is regarded as sacred or religiously significant within a particular belief system or tradition.
-
E.
hasSummitVillage
Indicates that an entity has an associated village located at or near its summit.
- 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_69f76e0386688190b931bacdc145938c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7340e4819092a1a47f7028e63f |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79ec14ce08190b22cee0b40d33743 |
completed | May 3, 2026, 7:15 p.m. |
Created at: May 3, 2026, 4:04 p.m.