Triple
T4339260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RUC badge |
E97538
|
entity |
| Predicate | endOfOfficialUse |
P48547
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [RUC badge, endOfOfficialUse, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfOfficialUse Context triple: [RUC badge, endOfOfficialUse, 2001]
-
A.
endOfOfficialUseAsRomanStateOffice
Indicates the point in time when an office ceased to function as an official governmental position of the Roman state.
-
B.
endOf
chosen
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
C.
hasOfficialUse
Indicates that something is used in an authorized or formally recognized capacity, typically by an official body or for official purposes.
-
D.
endDateOfficialUse
Indicates the date on which the official use or validity of something (such as a document, status, or authorization) comes to an end.
-
E.
usedInOfficialDocumentsOf
Indicates that something (e.g., a term, symbol, or format) is employed within the formal or legally recognized documents issued by a particular entity or jurisdiction.
- 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_69b3454662a481908fbcd0bbfaa3a0a4 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3516dffb48190878f81ffe71a5e82 |
completed | March 12, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69b34f4fe1c481908d6d66e15697c04b |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:14 p.m.