Triple
T23547867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chanoines réguliers |
E577954
|
entity |
| Predicate | formeDeVie |
P73021
|
FINISHED |
| Object | vie commune de prière |
—
|
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: vie commune de prière | Statement: [Chanoines réguliers, formeDeVie, vie commune de prière]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formeDeVie Context triple: [Chanoines réguliers, formeDeVie, vie commune de prière]
-
A.
hasFormOfLife
chosen
Indicates that one entity possesses, exhibits, or is associated with a particular form or type of life.
-
B.
publicLife
Indicates that an entity is involved in activities, roles, or interactions that are conducted openly in the public sphere rather than in private life.
-
C.
lifeForm
Indicates that an entity is a living organism or belongs to a category of living organisms.
-
D.
followsLifeOf
Indicates that one entity’s narrative, development, or progression is tracked or depicted over the course of that entity’s life.
-
E.
livesAccordingTo
Indicates that an entity conducts its life or behavior in alignment with a specified principle, rule, belief system, or standard.
- 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.