Triple
T6218356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Linear Collider |
E139047
|
entity |
| Predicate | electronBeamPolarization |
P68962
|
FINISHED |
| Object | about 80 percent |
—
|
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: about 80 percent | Statement: [International Linear Collider, electronBeamPolarization, about 80 percent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electronBeamPolarization Context triple: [International Linear Collider, electronBeamPolarization, about 80 percent]
-
A.
beamParticle
Indicates that one entity directs or projects another entity as a beam-like stream or focused flow.
-
B.
beamLine
Indicates a relationship where one entity directs or projects a beam or focused line (such as light, energy, or signal) toward another entity.
-
C.
beamDynamicsFeature
Indicates a characteristic or aspect related to the behavior, motion, or interaction of beams within a dynamic system.
-
D.
beamEnergy
Indicates the amount of energy carried by or assigned to a beam in a physical or engineered system.
-
E.
beamCurrent
Indicates the amount of electric current carried by a directed beam (such as a particle or electron beam) in a system or experiment.
- 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_69c008aecb0c81909984b48f733ce8ae |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062a481908190a1418d9fcfaf8137 |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c965ac8190b938502fa8c74e1b |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:21 p.m.