Triple
T461728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanbury Brown and Twiss effect |
E7352
|
entity |
| Predicate | demonstratedWith |
P4540
|
FINISHED |
| Object | radio waves |
—
|
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: radio waves | Statement: [Hanbury Brown and Twiss effect, demonstratedWith, radio waves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demonstratedWith Context triple: [Hanbury Brown and Twiss effect, demonstratedWith, radio waves]
-
A.
demonstratedBy
Indicates that something is shown, proven, or made evident through the actions, behavior, or example of a particular entity.
-
B.
demonstratedAt
Indicates that an action, behavior, or capability was shown or exhibited at a particular event, location, or point in time.
-
C.
demonstratedConcept
Indicates that an entity has shown, illustrated, or made evident a particular concept through example, explanation, or action.
-
D.
demonstrationDate
Indicates the date on which a demonstration or protest event takes place or is scheduled to occur.
-
E.
displayedWith
chosen
Indicates that one entity is shown or presented together alongside another entity in the same context or view.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efbed5b88190a45716812eb4cfdf |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2ede8eac081908dffade6a5e7950b |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.