Triple
T4944354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solemnity |
E111009
|
entity |
| Predicate | mayBeTransferredTo |
P17241
|
FINISHED |
| Object | Sunday |
—
|
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: Sunday | Statement: [Solemnity, mayBeTransferredTo, Sunday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeTransferredTo Context triple: [Solemnity, mayBeTransferredTo, Sunday]
-
A.
hasTransfer
chosen
Indicates a relationship where something is moved or conveyed from one entity or location to another.
-
B.
allowsTransferTo
Indicates that one entity permits or enables the transfer of something (such as rights, funds, or data) to another specified entity.
-
C.
transfersAvailableAt
Indicates that one entity offers or supports the ability to transfer to another service, route, or mode at a specified location or context.
-
D.
nonTransferable
Indicates that a right, asset, or privilege cannot be legally or contractually transferred from one party to another.
-
E.
transferType
Indicates the specific method or category of how something is transferred from one entity to another.
- 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd70a8e5388190882831d7828441d3 |
completed | March 20, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:31 p.m.