Triple
T1265113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gospels and Acts |
E12582
|
entity |
| Predicate | canonicalOrderEnd |
P24895
|
FINISHED |
| Object | fifth book of the New Testament |
—
|
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 book of the New Testament | Statement: [Gospels and Acts, canonicalOrderEnd, fifth book of the New Testament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalOrderEnd Context triple: [Gospels and Acts, canonicalOrderEnd, fifth book of the New Testament]
-
A.
subsequentOrder
Indicates that one order occurs after or follows another order in sequence.
-
B.
establishedInOrder
Indicates that one entity was created, founded, or formally set up as a result of, or in accordance with, a specific order, directive, or mandate.
-
C.
hasEnding
Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
-
D.
orderedBy
Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
-
E.
endedWith
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
- F. None of above. chosen
Provenance (4 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4c03573a48190b5851f0a734c2d6f |
completed | March 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69a4bb7058e88190825b0cba5ee60b51 |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bc218cb8819090bff71ac7107a03 |
completed | March 1, 2026, 10:22 p.m. |
Created at: March 1, 2026, 7:50 p.m.