Triple
T19188680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theban desert |
E469769
|
entity |
| Predicate | timeOfMonasticFlourishing |
P7645
|
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: [Theban desert, timeOfMonasticFlourishing, 4th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfMonasticFlourishing Context triple: [Theban desert, timeOfMonasticFlourishing, 4th century]
-
A.
historicalEraOfMonastery
Indicates the historical era or period during which the monastery was founded, active, or most prominently associated.
-
B.
numberOfMonasteriesFounded
Indicates the total count of monasteries that a given entity has established or founded.
-
C.
hasMonasticHistory
Indicates that an entity has a historical association with monastic life, institutions, or traditions.
-
D.
organizedMonasticLifeCentury
chosen
Indicates the century during which an entity established or practiced an organized form of monastic life.
-
E.
monasteryEstablished
Indicates that a monastery was founded or formally established at a particular time, place, or by a specific agent.
- 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f8a01d08819081608a6ab8c6e705 |
completed | April 20, 2026, 9:57 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.