Triple
T1462772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rayleigh–Jeans law at low frequencies |
E31549
|
entity |
| Predicate | failsAt |
P8788
|
FINISHED |
| Object | high frequencies |
—
|
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: high frequencies | Statement: [Rayleigh–Jeans law at low frequencies, failsAt, high frequencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: failsAt Context triple: [Rayleigh–Jeans law at low frequencies, failsAt, high frequencies]
-
A.
failsWhen
chosen
Indicates that a particular action, process, or condition does not succeed under the specified circumstances or triggers.
-
B.
missionFailure
Indicates that an attempted mission or operation did not achieve its intended objectives or outcome.
-
C.
launchFailures
Indicates that attempts to initiate or start an operation, process, or system have failed.
-
D.
rejectedAt
Indicates the time or date at which something (such as a request, application, or proposal) was formally rejected.
-
E.
failedLaunches
Indicates that one or more attempts to launch something (e.g., a product, project, or mission) did not succeed.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5b6e36c81909c47b2f7e66f17d7 |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48121e48190946c23c583e5fb64 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.