Triple
T4767609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massacre of the Innocents |
E105849
|
entity |
| Predicate | canonicalReference |
P5454
|
FINISHED |
| Object | Matthew 2:16–18 |
—
|
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: Matthew 2:16–18 | Statement: [Massacre of the Innocents, canonicalReference, Matthew 2:16–18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalReference Context triple: [Massacre of the Innocents, canonicalReference, Matthew 2:16–18]
-
A.
standardReference
Indicates that one entity serves as the authoritative or canonical reference or benchmark for interpreting, validating, or comparing another entity.
-
B.
hasCanonicalReference
chosen
Indicates that one entity serves as the authoritative or standard reference source for another entity.
-
C.
canonicalText
Indicates that a standardized, authoritative textual representation is associated with an entity or expression.
-
D.
primaryReference
Indicates that one entity serves as the main or authoritative source of information or citation for another entity.
-
E.
canonicalStatus
Indicates the formal or official standing of an entity within an established authoritative or normative system.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.