Triple
T6235897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canons Regular |
E139476
|
entity |
| Predicate | livesAccordingTo |
P69681
|
FINISHED |
| Object | constitutions of the order |
—
|
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: constitutions of the order | Statement: [Canons Regular, livesAccordingTo, constitutions of the order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livesAccordingTo Context triple: [Canons Regular, livesAccordingTo, constitutions of the order]
-
A.
lifeDetails
Indicates that additional information or specific aspects about an entity’s life (such as background, experiences, or personal history) are being described.
-
B.
livesOn
Indicates that one entity resides or has its home on or atop another entity (such as a surface, structure, or geographic feature).
-
C.
traditionallyLivedTo
Indicates that an entity customarily or historically resided in a particular place or environment over an extended period.
-
D.
alsoLivesIn
Indicates that two or more entities share the same place of residence.
-
E.
followsLifeOf
Indicates that one entity’s narrative, development, or progression is tracked or depicted over the course of that entity’s life.
- F. None of above. chosen
Provenance (4 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_69c008b0e7ac8190808a59573ee646f3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062f236608190997e77b41095883f |
completed | March 22, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69c05601de6481909d0880048fd7b49a |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c05707d5408190a1d0fd80414ad957 |
completed | March 22, 2026, 8:54 p.m. |
Created at: March 22, 2026, 4:23 p.m.