Triple
T28188343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KamLAND experiment |
E716234
|
entity |
| Predicate | hasDetectorMass |
P100393
|
FINISHED |
| Object | about 1 kiloton of liquid scintillator |
—
|
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 1 kiloton of liquid scintillator | Statement: [KamLAND experiment, hasDetectorMass, about 1 kiloton of liquid scintillator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDetectorMass Context triple: [KamLAND experiment, hasDetectorMass, about 1 kiloton of liquid scintillator]
-
A.
hasMasses
chosen
Indicates that one entity possesses or is associated with one or more masses (quantities of matter).
-
B.
hasTypeOfMass
Indicates that one entity possesses or is characterized by a particular kind or category of mass.
-
C.
hasMassScale
Indicates that an entity is associated with a particular mass measurement scale or system used to quantify its mass.
-
D.
isDetector
Indicates that one entity functions as a detector for, or is responsible for detecting, another entity or phenomenon.
-
E.
hasFarDetector
Indicates that an entity is equipped with or associated with a detector positioned at a relatively large distance from a reference point or source.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 27, 2026, 10:24 p.m.