Triple
T34373138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pachomian monastic federation |
E882215
|
entity |
| Predicate | hasCentralMonasteryAt |
P132651
|
FINISHED |
| Object | Tabennesi |
—
|
NE NERFINISHED |
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: Tabennesi | Statement: [Pachomian monastic federation, hasCentralMonasteryAt, Tabennesi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralMonasteryAt Context triple: [Pachomian monastic federation, hasCentralMonasteryAt, Tabennesi]
-
A.
mainMonasteryCountry
Indicates the country in which a monastery’s primary or main location is situated.
-
B.
mainMonasteryLocation
chosen
Indicates the place where a religious order’s primary or central monastery is situated.
-
C.
hasMainMonasteryInExile
Indicates that an entity’s primary monastery is located outside its original or traditional homeland, in a place of exile.
-
D.
containsMonastery
Indicates that one entity includes or encompasses a monastery within its boundaries or composition.
-
E.
hasNearbyMonastery
Indicates that one entity is located close to or in the vicinity of a monastery.
- 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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 1, 2026, 1:59 a.m.