Triple
T29100354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Extra Half-Brite |
E736622
|
entity |
| Predicate | halfBrightComputation |
P166548
|
FINISHED |
| Object | performed in hardware, not in software |
—
|
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: performed in hardware, not in software | Statement: [Extra Half-Brite, halfBrightComputation, performed in hardware, not in software]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: halfBrightComputation Context triple: [Extra Half-Brite, halfBrightComputation, performed in hardware, not in software]
-
A.
halfBrightIntensity
Indicates that one entity’s brightness or light intensity is exactly half that of another entity.
-
B.
halfBrightColorsDerivedFrom
chosen
Indicates that the subject’s half-bright color variants are derived from or computed based on the object’s colors.
-
C.
halfLightRadius
Indicates the radius within which half of an object's total emitted light is contained.
-
D.
isBright
Indicates that an entity emits or reflects a high level of light, making it visually intense or luminous.
-
E.
isBrighterThan
Indicates that one entity emits or reflects more light, or appears more luminous, than 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 11:11 a.m.