Triple
T17764487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Experimental Area 2 |
E443467
|
entity |
| Predicate | supportsDetectorType |
P128687
|
FINISHED |
| Object | gamma-ray detectors |
—
|
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: gamma-ray detectors | Statement: [Experimental Area 2, supportsDetectorType, gamma-ray detectors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDetectorType Context triple: [Experimental Area 2, supportsDetectorType, gamma-ray detectors]
-
A.
supportsDetectorTypes
chosen
Indicates that an entity is compatible with and can operate using specific types or categories of detectors.
-
B.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
C.
supportsTestType
Indicates that one entity is capable of handling, executing, or being compatible with a specified type of test.
-
D.
supportsDriverType
Indicates that one entity is compatible with, or able to operate using, a specified type of driver.
-
E.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485fb2a3c81908887d1d36aee942d |
completed | April 19, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:11 a.m.