Triple
T8585542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Registry Room |
E203296
|
entity |
| Predicate | endUseDateAsMainProcessingCenter |
P6544
|
FINISHED |
| Object | 1954 |
—
|
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: 1954 | Statement: [Registry Room, endUseDateAsMainProcessingCenter, 1954]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endUseDateAsMainProcessingCenter Context triple: [Registry Room, endUseDateAsMainProcessingCenter, 1954]
-
A.
usedUntil
chosen
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
-
B.
startUseBy
Indicates the point in time from which an entity begins to be used by another entity or for a particular purpose.
-
C.
processingUse
Indicates that one entity uses or applies another entity as part of a processing or transformation activity.
-
D.
managedUntil
Indicates that one entity was responsible for managing or overseeing another entity up to a specific point in time.
-
E.
endUseForIMT
Indicates that something serves as the final or intended end use for an intermediate material or technology (IMT).
- 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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46c5e8888190b721e791c449b0df |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
Created at: March 30, 2026, 6:22 p.m.