Triple
T14550209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Clot |
E341394
|
entity |
| Predicate | hasApproximateChronologicalOrderOfRevelation |
P48135
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [The Clot, hasApproximateChronologicalOrderOfRevelation, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateChronologicalOrderOfRevelation Context triple: [The Clot, hasApproximateChronologicalOrderOfRevelation, 1]
-
A.
chronologicalOrderInGospels
Indicates that the events or elements are arranged in the sequence in which they occur within the Gospel narratives.
-
B.
chronologicalOrderOfGospels
Indicates the temporal sequence in which the Gospels are believed or asserted to have been written or occurred relative to one another.
-
C.
orderOfRevelation
chosen
Indicates the sequence in which multiple related items, events, or pieces of information are revealed or disclosed.
-
D.
chronologicallyOrdered
Indicates that the related entities are arranged in the order in which they occur in time.
-
E.
occasionOfRevelation
Indicates the specific event, situation, or context during which a revelation or disclosure took place.
- 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb2ed2b4c8190945bd26531c71f1f |
completed | April 14, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:23 a.m.