Triple
T27176245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Responsorial Psalm |
E683050
|
entity |
| Predicate | mayBeTakenFrom |
P25436
|
FINISHED |
| Object | biblical canticles |
—
|
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: biblical canticles | Statement: [Responsorial Psalm, mayBeTakenFrom, biblical canticles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeTakenFrom Context triple: [Responsorial Psalm, mayBeTakenFrom, biblical canticles]
-
A.
mayTake
Indicates that an entity is permitted or allowed to take, enroll in, or participate in another entity (such as a course, resource, or opportunity).
-
B.
canBeTakenQuickly
Indicates that the action or resource can be obtained, completed, or utilized in a short amount of time.
-
C.
mayBeReservedBy
Indicates that an entity is eligible or allowed to be reserved by another entity, without asserting that the reservation has actually occurred.
-
D.
canBeObtainedFrom
chosen
Indicates that one entity is derivable, producible, or acquirable from another entity as a source or origin.
-
E.
isTakenBy
Indicates that something (such as an object, resource, or opportunity) is received, acquired, or accepted by a particular entity.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 9:26 a.m.