Triple
T26394667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GLEEP research reactor |
E663514
|
entity |
| Predicate | lifetimeUse |
P160496
|
FINISHED |
| Object | training of reactor operators |
—
|
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: training of reactor operators | Statement: [GLEEP research reactor, lifetimeUse, training of reactor operators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifetimeUse Context triple: [GLEEP research reactor, lifetimeUse, training of reactor operators]
-
A.
durationOfUse
Indicates the length of time for which something is used or remains in use.
-
B.
lifetimeRequirement
Indicates that one entity imposes or must satisfy a specified duration or lifespan condition in relation to another entity or context.
-
C.
usedUntil
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
-
D.
lifetimeFree
Indicates that an entity is provided without cost for the entire duration of its existence or validity, with no time-based charges ever applied.
-
E.
typicalUseDays
Indicates the usual or expected number of days over which something is used or intended to be used.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610c1b57081909b603c41b3c0e5e0 |
completed | May 2, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f6018ceb1c8190a6a5f84071659a96 |
completed | May 2, 2026, 1:52 p.m. |
Created at: April 26, 2026, 11:28 p.m.