Triple
T22984188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyndall effect |
E571557
|
entity |
| Predicate | strongerFor |
P73273
|
FINISHED |
| Object | shorter wavelengths of visible light |
—
|
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: shorter wavelengths of visible light | Statement: [Tyndall effect, strongerFor, shorter wavelengths of visible light]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strongerFor Context triple: [Tyndall effect, strongerFor, shorter wavelengths of visible light]
-
A.
strongerAt
chosen
Indicates that one entity has greater strength, power, or effectiveness than another in a specified context, condition, or domain.
-
B.
strongerDuring
Indicates that one entity exhibits greater strength or intensity than another specifically during a given time period or event.
-
C.
strengthensFrom
Indicates that one entity becomes stronger, more effective, or more intense as a result of influence, support, or input from another entity.
-
D.
strongerThan
Indicates that one entity possesses greater strength, power, or intensity than another.
-
E.
strengthens
Indicates that one entity increases the power, effectiveness, or resilience of another.
- 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18298637c819086fca34d55bad22d |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:49 p.m.