Triple
T23547803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premonstratensians |
E577952
|
entity |
| Predicate | hasNotableAbbey |
P113881
|
FINISHED |
| Object | Strahov Monastery |
—
|
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: Strahov Monastery | Statement: [Premonstratensians, hasNotableAbbey, Strahov Monastery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableAbbey Context triple: [Premonstratensians, hasNotableAbbey, Strahov Monastery]
-
A.
hadAbbey
chosen
Indicates that an entity possessed, was associated with, or was the site of a particular abbey.
-
B.
hasNotableCathedral
Indicates that a place or entity possesses a cathedral that is recognized for its historical, architectural, cultural, or religious significance.
-
C.
hasAbbess
Indicates that a religious community, convent, or abbey is led or overseen by a specific abbess.
-
D.
hasNotableTemple
Indicates that an entity is associated with a temple that is recognized as particularly important, famous, or significant.
-
E.
abbeyLocation
Indicates the geographical place where an abbey is situated or located.
- 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aecc2af08190aec07cf9126d4e72 |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:11 p.m.