Triple
T14752971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sevanavank Monastery |
E346656
|
entity |
| Predicate | originalLocationType |
P115655
|
FINISHED |
| Object | island |
—
|
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: island | Statement: [Sevanavank Monastery, originalLocationType, island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalLocationType Context triple: [Sevanavank Monastery, originalLocationType, island]
-
A.
originalLocationStatus
Indicates the status or condition of an entity’s original location, such as whether it remains, has changed, or is otherwise affected.
-
B.
originalLocationEvent
Indicates that an event occurred at or is associated with the place where an entity was originally located or originated.
-
C.
originalType
Indicates that one entity represents the initial or source type from which another entity is derived, transformed, or reclassified.
-
D.
arrivalLocationType
Indicates the type or category of place where an arrival occurs in the described relationship or event.
-
E.
originalLocationCountry
Indicates the country where an entity was originally located or from which it initially originated.
- 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.