Triple
T22842132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OPERA |
E566109
|
entity |
| Predicate | dataAnalysisMethod |
P28210
|
FINISHED |
| Object | emulsion tracking of charged particles |
—
|
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: emulsion tracking of charged particles | Statement: [OPERA, dataAnalysisMethod, emulsion tracking of charged particles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataAnalysisMethod Context triple: [OPERA, dataAnalysisMethod, emulsion tracking of charged particles]
-
A.
analysisType
Indicates the specific kind or category of analysis being applied or performed in relation to an entity or dataset.
-
B.
dataAnalysisEnd
Indicates that a data analysis process or activity has been completed or brought to an end.
-
C.
helpsAnalyze
Indicates that one entity assists another in examining, interpreting, or understanding something in a more detailed or effective way.
-
D.
statisticsConsidered
Indicates that certain statistics are taken into account or used as a basis in a decision, analysis, or evaluation involving the related entities.
-
E.
methodologyType
chosen
Indicates the specific kind or category of method or procedure used in carrying out an activity or study.
- 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_69e245869e188190a196584f36e682da |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e855abc8190b9cf8cc515090a7f |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:35 p.m.