Triple
T33030439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Monte Vergine |
E845148
|
entity |
| Predicate | hasMotherHouse |
P10994
|
FINISHED |
| Object | Abbey of Montevergine |
—
|
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: Abbey of Montevergine | Statement: [Order of Monte Vergine, hasMotherHouse, Abbey of Montevergine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMotherHouse Context triple: [Order of Monte Vergine, hasMotherHouse, Abbey of Montevergine]
-
A.
hasParentHouse
chosen
Indicates that an entity is associated with or belongs to a specific parent house within a hierarchical or familial structure.
-
B.
hasMotherhouseLocation
Indicates the location where an organization’s primary or founding house (motherhouse) is situated.
-
C.
hasMotherhouseType
Indicates the specific type or classification of a religious community’s motherhouse associated with an entity.
-
D.
maternalHouse
Indicates the house or family line associated with an entity’s mother, typically representing maternal ancestry or origin.
-
E.
hasClanMother
Indicates that an individual belongs to or is under the authority or lineage of a specific clan mother within a clan-based social structure.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: May 1, 2026, 1:24 a.m.