Triple
T5815575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stavrovouni Monastery |
E128976
|
entity |
| Predicate | traditionallyFoundedIn |
P13132
|
FINISHED |
| Object | 4th century |
—
|
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: 4th century | Statement: [Stavrovouni Monastery, traditionallyFoundedIn, 4th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyFoundedIn Context triple: [Stavrovouni Monastery, traditionallyFoundedIn, 4th century]
-
A.
foundedBefore
Indicates that one entity was established or created at an earlier time than the other entity.
-
B.
traditionallyFoundIn
chosen
Indicates that something is customarily or historically located, used, or present within a particular place, context, or setting.
-
C.
foundedFrom
Indicates that an entity was established or originated starting from a particular source, place, or prior entity.
-
D.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
-
E.
historicallyBasedIn
Indicates that one entity is located in or associated with a place as its base of operations during a specific historical period.
- 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_69c0084788848190bcf71f6bc5d71597 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0333fdd7081908d829265caa2ac11 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:53 p.m.