Triple
T23547866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chanoines réguliers |
E577954
|
entity |
| Predicate | vieEnCommunauté |
P152752
|
FINISHED |
| Object | oui |
—
|
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: oui | Statement: [Chanoines réguliers, vieEnCommunauté, oui]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vieEnCommunauté Context triple: [Chanoines réguliers, vieEnCommunauté, oui]
-
A.
inGameZone
Indicates that an entity is located within a defined game zone or area of the game world.
-
B.
homeGameWorld
Indicates that a game or match is being played in the home world or home venue associated with a particular team or participant.
-
C.
gamingSpace
Indicates a relationship where a space, area, or environment is designated or used specifically for gaming activities.
-
D.
cooperativePlay
Indicates that two or more entities are engaging in a shared, mutually coordinated activity or game toward a common goal.
-
E.
sharesGameClientWith
Indicates that two entities use or are associated with the same game client software or instance.
- 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_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. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:11 p.m.