Triple
T10838483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aduard |
E255824
|
entity |
| Predicate | monasteryFoundedInCentury |
P53542
|
FINISHED |
| Object | 12th 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: 12th century | Statement: [Aduard, monasteryFoundedInCentury, 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monasteryFoundedInCentury Context triple: [Aduard, monasteryFoundedInCentury, 12th century]
-
A.
monasteryEstablished
Indicates that a monastery was founded or formally established at a particular time, place, or by a specific agent.
-
B.
numberOfMonasteriesFounded
Indicates the total count of monasteries that a given entity has established or founded.
-
C.
historicalEraOfMonastery
chosen
Indicates the historical era or period during which the monastery was founded, active, or most prominently associated.
-
D.
placeOfMonasticFoundation
Indicates the location where a monastic community or monastery was originally established or founded.
-
E.
monastery
Indicates that an entity is or functions as a monastery, typically a religious community or building where monastics live and practice.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d747002b3081908726901ee83d8f38 |
completed | April 9, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.