Triple
T16127200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Sunday of the Passion |
E391301
|
entity |
| Predicate | hasCurrentCommonName |
P1354
|
FINISHED |
| Object | Fifth Sunday of Lent |
—
|
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: Fifth Sunday of Lent | Statement: [First Sunday of the Passion, hasCurrentCommonName, Fifth Sunday of Lent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrentCommonName Context triple: [First Sunday of the Passion, hasCurrentCommonName, Fifth Sunday of Lent]
-
A.
includesCommonName
Indicates that one entity contains or specifies a commonly used (non-scientific) name for another entity.
-
B.
commonNameOf
chosen
Indicates that one entity is the commonly used or popular name by which the other entity is known.
-
C.
commonName
Indicates that one entity is the commonly used or vernacular name by which the other entity is known.
-
D.
commonNameDerivedFrom
Indicates that the commonly used name of one entity originates from, or is derived based on, another entity.
-
E.
moreCommonPublicName
Indicates that one name is used more frequently or popularly in public contexts than another alternative name for the same 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e20205bed48190a6930439738da191 |
completed | April 17, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.