Triple
T34373233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tabennisi |
E882217
|
entity |
| Predicate | hasMonasticRuleFeature |
P104108
|
FINISHED |
| Object | strict obedience |
—
|
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: strict obedience | Statement: [Tabennisi, hasMonasticRuleFeature, strict obedience]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonasticRuleFeature Context triple: [Tabennisi, hasMonasticRuleFeature, strict obedience]
-
A.
hasMonasticComplexFeature
Indicates that a monastic complex includes or is characterized by a particular architectural or functional feature.
-
B.
hasMonasticForm
Indicates that an entity possesses or is associated with a specific monastic form, style, or mode of religious life.
-
C.
hasMonasticHistory
Indicates that an entity has a historical association with monastic life, institutions, or traditions.
-
D.
monasticRequirement
chosen
Indicates that one entity imposes, specifies, or embodies a rule, obligation, or condition that must be fulfilled within a monastic or religious order.
-
E.
hasMonasticName
Indicates that an entity possesses a specific name adopted or assigned within a monastic or religious order.
- 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_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
Created at: May 1, 2026, 1:59 a.m.