Triple
T18314873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIRC2 camera |
E438729
|
entity |
| Predicate | hasDetectorFormat |
P41862
|
FINISHED |
| Object | 1024 x 1024 pixels |
—
|
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: 1024 x 1024 pixels | Statement: [NIRC2 camera, hasDetectorFormat, 1024 x 1024 pixels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDetectorFormat Context triple: [NIRC2 camera, hasDetectorFormat, 1024 x 1024 pixels]
-
A.
detectorFormat
chosen
Indicates the specific data or signal representation used by a detector to encode or output its measurements.
-
B.
hasWorkingFormat
Indicates that one entity possesses or is associated with a functional or operational format of another entity.
-
C.
supportsDetectorTypes
Indicates that an entity is compatible with and can operate using specific types or categories of detectors.
-
D.
hasConfigurationFormat
Indicates that an entity uses or is associated with a specific configuration format for its settings or parameters.
-
E.
hasFileFormat
Indicates that one entity (typically a digital file or resource) is encoded, stored, or represented using a specific file format defined by the other 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5021cc70c8190bf43bd75e4af7381 |
completed | April 19, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.