Triple
T22507091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fraunhofer lines |
E556416
|
entity |
| Predicate | appearAs |
P24836
|
FINISHED |
| Object | dark lines on a continuous spectrum |
—
|
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: dark lines on a continuous spectrum | Statement: [Fraunhofer lines, appearAs, dark lines on a continuous spectrum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearAs Context triple: [Fraunhofer lines, appearAs, dark lines on a continuous spectrum]
-
A.
appearsAs
chosen
Indicates that one entity is presented, perceived, or manifested in the form, role, or guise of another entity.
-
B.
appearTo
Indicates that something gives the impression or seems to be a certain way to an observer, without confirming that it actually is so.
-
C.
appearedWith
Indicates that two entities were present or participated together in the same context, event, or medium.
-
D.
apparentIn
Indicates that something is visibly present, manifested, or evident within or through another thing or context.
-
E.
mayAppear
Indicates that an entity is allowed or has the possibility to be present or occur in association with another entity or context.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d5cddf88190821d9c9fdee84160 |
completed | April 29, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:50 p.m.