Triple
T19154761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Friday devotion |
E468902
|
entity |
| Predicate | requiresSequence |
P100
|
FINISHED |
| Object | nine consecutive first Fridays |
—
|
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: nine consecutive first Fridays | Statement: [First Friday devotion, requiresSequence, nine consecutive first Fridays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSequence Context triple: [First Friday devotion, requiresSequence, nine consecutive first Fridays]
-
A.
requiresSubSequenceConstraint
Indicates that one element must occur as a subsequence within another, enforcing an ordered containment constraint between them.
-
B.
isSequence
Indicates that one entity is an ordered list or succession of elements arranged in a specific, meaningful order.
-
C.
isSequenceOf
Indicates that one entity occurs in a specific order directly following or as part of an ordered list relative to another entity.
-
D.
sequenceWith
Indicates that one entity occurs in a specific order directly before or after another entity as part of a defined sequence.
-
E.
requires
chosen
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eeb81bf08190b0352137eb4a5763 |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.