Triple
T6088121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timepix pixel detector |
E135689
|
entity |
| Predicate | hasReadoutMode |
P12713
|
FINISHED |
| Object | time-over-threshold |
—
|
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: time-over-threshold | Statement: [Timepix pixel detector, hasReadoutMode, time-over-threshold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReadoutMode Context triple: [Timepix pixel detector, hasReadoutMode, time-over-threshold]
-
A.
supportsObservationModes
Indicates that one entity provides or is compatible with specific modes or methods of observation used by another entity.
-
B.
hasWorkingMode
chosen
Indicates that an entity operates under or supports a particular mode or configuration of functioning.
-
C.
hasModeConnection
Indicates a relationship where one entity is linked to another through a specific mode, method, or type of connection.
-
D.
hasReadingType
Indicates that an entity is associated with a specific category or mode of reading, such as a particular interpretation, format, or type of reading measurement.
-
E.
hasOuterDisplay
Indicates that one entity serves as the external or outward-facing display component of another entity.
- 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_69c0087bcc788190b20f093d3a6c60ec |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c057a6f7588190b265d6005fbaf6b3 |
completed | March 22, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69c049f3b1ec8190bea67a7bec6442a5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:12 p.m.