Triple
T28188314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KamLAND experiment |
E716234
|
entity |
| Predicate | basedOnDetectorType |
P132777
|
FINISHED |
| Object | liquid scintillator detector |
—
|
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: liquid scintillator detector | Statement: [KamLAND experiment, basedOnDetectorType, liquid scintillator detector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnDetectorType Context triple: [KamLAND experiment, basedOnDetectorType, liquid scintillator detector]
-
A.
detectorType
Indicates the specific kind or category of detector associated with an entity or measurement.
-
B.
isDetector
Indicates that one entity functions as a detector for, or is responsible for detecting, another entity or phenomenon.
-
C.
primaryDetectorType
chosen
Indicates the main kind or category of detector that is used as the primary sensing or measurement component in a given context.
-
D.
basedOnType
Indicates that one entity is derived, determined, or classified according to the type or category of another entity.
-
E.
mainDetector
Indicates that an entity serves as the primary or principal detector in relation to another entity or system.
- 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_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 27, 2026, 10:24 p.m.