Triple
T35184782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Our Lady of the Roses |
E1015954
|
entity |
| Predicate | involvesLayParticipation |
P4470
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Our Lady of the Roses, involvesLayParticipation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesLayParticipation Context triple: [Our Lady of the Roses, involvesLayParticipation, yes]
-
A.
establishesParticipationIn
Indicates that one entity formally creates or defines another entity’s involvement in an activity, event, or group.
-
B.
councilParticipation
Indicates that an entity takes part in, or is a member of, a council or governing body.
-
C.
participation
chosen
Indicates that an entity takes part in, contributes to, or is involved in a shared activity, event, or process with others.
-
D.
governingBodyInvolvement
Indicates the extent or manner in which a governing body participates in, oversees, or influences a particular activity, decision, or entity.
-
E.
participatingLevel
Indicates the degree or extent to which an entity is involved or engaged in a particular activity, event, or process.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: May 3, 2026, 4:02 p.m.