Triple
T3113359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solemnity of Mary, Mother of God |
E65000
|
entity |
| Predicate | hasPrincipalMassReading |
P45406
|
FINISHED |
| Object | Numbers 6:22–27 |
—
|
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: Numbers 6:22–27 | Statement: [Solemnity of Mary, Mother of God, hasPrincipalMassReading, Numbers 6:22–27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrincipalMassReading Context triple: [Solemnity of Mary, Mother of God, hasPrincipalMassReading, Numbers 6:22–27]
-
A.
hasMass_kg
Indicates that an entity possesses a specific mass measured in kilograms.
-
B.
givesMassTo
Indicates that one entity transfers or assigns a certain amount of mass to another entity.
-
C.
hasMeasurement
Indicates that an entity is associated with a specific measured value, often including a unit or measurement context.
-
D.
hasMeter
Indicates that one entity possesses, uses, or is associated with a specific meter (a measuring device or metrical pattern).
-
E.
requiresWeighIn
Indicates that one entity must provide an opinion, decision, or input before another entity’s action or process can proceed.
- 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_69ad857fcc088190b0c4d45a5cde6f61 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada43c79448190aa72f707319e8c5e |
completed | March 8, 2026, 4:30 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f7c21c819087e9992f5fe30a37 |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:04 p.m.