Triple
T19065754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exodus 13 |
E466652
|
entity |
| Predicate | canonicalPosition |
P21161
|
FINISHED |
| Object | 13th chapter of Exodus |
—
|
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: 13th chapter of Exodus | Statement: [Exodus 13, canonicalPosition, 13th chapter of Exodus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalPosition Context triple: [Exodus 13, canonicalPosition, 13th chapter of Exodus]
-
A.
hasCanonicalPosition
chosen
Indicates that an entity occupies a standard, officially recognized, or authoritative position or location within a defined structure or system.
-
B.
corePosition
Indicates that one entity occupies the central or primary position within another entity or structure.
-
C.
classPosition
Indicates the relative ordering or rank of an entity within a class, group, or sequence.
-
D.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
E.
currentPosition
Indicates the present role, job, or status an entity currently holds within a given context.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e198621481908618f65dd01746fc |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.