Triple
T680126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linac2 |
E13162
|
entity |
| Predicate | successorEnergy |
P17460
|
FINISHED |
| Object | 160 MeV (Linac4 output energy) |
—
|
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: 160 MeV (Linac4 output energy) | Statement: [Linac2, successorEnergy, 160 MeV (Linac4 output energy)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorEnergy Context triple: [Linac2, successorEnergy, 160 MeV (Linac4 output energy)]
-
A.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
B.
successorCompetition
Indicates that one competition directly follows another in sequence, serving as its successor in a series or timeline.
-
C.
successorFunction
Indicates the relationship where one entity is defined as the immediate next or following element in a sequence or ordered set relative to another.
-
D.
successorDivision
Indicates that one division is the organizational successor that continues or replaces the role, functions, or identity of another division.
-
E.
successorOperator
Indicates that one operator directly follows another in a defined sequence or ordering.
- 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_69a4933d3bf88190972041cd8cf143b9 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a04f4efc819082767a7517fa760a |
completed | March 1, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69a49d1d79608190a849ba9ffad2879d |
completed | March 1, 2026, 8:10 p.m. |
| PDg | Predicate description generation | batch_69a49df19c9481909cc9bc33ed7f011b |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:36 p.m.