Triple
T2414111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fratres omnes |
E52262
|
entity |
| Predicate | hasSupersedingDocument |
P9033
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Fratres omnes, hasSupersedingDocument, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupersedingDocument Context triple: [Fratres omnes, hasSupersedingDocument, none]
-
A.
wasSupersededBy
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
B.
successorDocument
chosen
Indicates that one document directly follows and replaces another in a version or revision sequence.
-
C.
supersededInPrecisionBy
Indicates that one entity’s level of precision has been replaced or overtaken by another entity’s greater precision.
-
D.
abolishedByDocument
Indicates that something (such as a law, rule, or institution) is formally ended, revoked, or nullified through the authority of a specific document.
-
E.
hasSubsequentStandard
Indicates that one standard is followed or superseded by another standard that comes after it in sequence or version.
- 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_69ab495622948190bc6bc6e4cddaf645 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc94a6458819087b8c4fe81a2d031 |
completed | March 7, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69abc5a6cbd0819086c0716e266b7ebb |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:41 p.m.