Triple
T21472616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon Missae |
E529768
|
entity |
| Predicate | largelyFixedBy |
P144493
|
FINISHED |
| Object | 6th century |
—
|
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: 6th century | Statement: [Canon Missae, largelyFixedBy, 6th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: largelyFixedBy Context triple: [Canon Missae, largelyFixedBy, 6th century]
-
A.
fixedBy
Indicates that one entity is repaired, corrected, or resolved through the action or intervention of another entity.
-
B.
usedToFix
Indicates that one entity serves as a tool, method, or resource employed to repair, correct, or resolve a problem or defect in another entity.
-
C.
repairedIn
Indicates that an item or object underwent repair within a specified location or during a particular time period.
-
D.
amendedFor
Indicates that one entity has been modified or revised specifically to address, correct, or accommodate another entity.
-
E.
fixation
Indicates an intense, often obsessive focus or attachment of one entity toward another entity, object, or idea.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea14756081908c615590c68904d5 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e6386c5a4481909c37f7de7e9fc025 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 16, 2026, 6:19 p.m.