Triple
T25760616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Prayer |
E648729
|
entity |
| Predicate | mayBeAdaptedTo |
P4577
|
FINISHED |
| Object | liturgical season |
—
|
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: liturgical season | Statement: [Universal Prayer, mayBeAdaptedTo, liturgical season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeAdaptedTo Context triple: [Universal Prayer, mayBeAdaptedTo, liturgical season]
-
A.
mayAdapt
Indicates that one entity is permitted or allowed to modify, adjust, or alter another entity.
-
B.
adaptedTo
chosen
Indicates that one entity has been modified, adjusted, or evolved to function effectively within the conditions, requirements, or characteristics defined by another entity.
-
C.
canBeAdaptedBy
Indicates that one entity is capable of being modified, adjusted, or tailored for use by another entity.
-
D.
adaptedWithin
Indicates that one entity has been modified, adjusted, or tailored to function appropriately within the context, scope, or boundaries defined by another entity.
-
E.
hasBeenAdaptedBy
Indicates that an original work has been transformed or re-created into a new form or medium by a particular adapter.
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603bb02288190b40cedbed5b9651d |
completed | May 2, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 22, 2026, 5:05 a.m.