Triple
T14752972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sevanavank Monastery |
E346656
|
entity |
| Predicate | currentLocationType |
P115656
|
FINISHED |
| Object | peninsula |
—
|
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: peninsula | Statement: [Sevanavank Monastery, currentLocationType, peninsula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentLocationType Context triple: [Sevanavank Monastery, currentLocationType, peninsula]
-
A.
locationDuringUse
Indicates the place or spatial context where an entity is situated specifically while it is being used or in active operation.
-
B.
locationStatus
Indicates the current state or condition of an entity with respect to a specific location (e.g., present, absent, en route, or unknown).
-
C.
currentLocationSince
Indicates the point in time since which an entity has been at its current location.
-
D.
locationNowCalled
Indicates that a location is currently known or referred to by a different (typically newer) name than it was previously.
-
E.
presentDayLocationCorrespondsTo
Indicates that the current, real-world location of an entity matches or aligns with a specified reference location.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7d40efc8190bb1be34c19a2b57c |
completed | April 14, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:30 a.m.