Triple
T3671528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Week of Prayer for Christian Unity |
E77890
|
entity |
| Predicate | hasTypicalStartDate |
P32533
|
FINISHED |
| Object | 18 January |
—
|
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: 18 January | Statement: [Week of Prayer for Christian Unity, hasTypicalStartDate, 18 January]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalStartDate Context triple: [Week of Prayer for Christian Unity, hasTypicalStartDate, 18 January]
-
A.
typicalStartPeriod
chosen
Indicates the usual or standard time period during which something begins or is initiated.
-
B.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
C.
hasBaseDate
Indicates that an entity is associated with a specific reference or starting date used as the basis for related calculations, schedules, or validity periods.
-
D.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
E.
typicalDates
Indicates the usual or standard dates during which something typically occurs, is valid, or is scheduled.
- 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc42de1bc819090e19dd0805f13a1 |
completed | March 8, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69adb84a20288190a092e4a1b045fe3f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.