Triple
T2706123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIRCam |
E59344
|
entity |
| Predicate | hasFilterType |
P42116
|
FINISHED |
| Object | broad-band filters |
—
|
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: broad-band filters | Statement: [NIRCam, hasFilterType, broad-band filters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFilterType Context triple: [NIRCam, hasFilterType, broad-band filters]
-
A.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
B.
hasCriterionType
Indicates that something is associated with or classified by a specific type of criterion used for evaluation or decision-making.
-
C.
hasFlowType
Indicates the type or category of flow associated with or exhibited by an entity.
-
D.
hasCurrentType
Indicates that an entity currently possesses or is classified under a specific type or category, as opposed to past or potential types.
-
E.
hasDisplayType
Indicates the type or category of display associated with an entity, such as the format, mode, or presentation style used to show its content.
- F. None of above. chosen
Provenance (4 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda559a908190ad5d92c11a398a03 |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd82062988190b4292f242ad70b2c |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd9ceec708190aa162399023b2273 |
completed | March 7, 2026, 7:54 a.m. |
Created at: March 6, 2026, 9:55 p.m.