Triple
T34616346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DONUT |
E888874
|
entity |
| Predicate | interactionSignature |
P196055
|
FINISHED |
| Object | short tau track followed by decay kink |
—
|
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: short tau track followed by decay kink | Statement: [DONUT, interactionSignature, short tau track followed by decay kink]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interactionSignature Context triple: [DONUT, interactionSignature, short tau track followed by decay kink]
-
A.
interactionMechanism
Indicates the process or means by which one entity affects, influences, or interacts with another.
-
B.
interactionBetween
Indicates a reciprocal or mutual action, influence, or communication occurring between two or more entities.
-
C.
interactionWithHumans
Indicates a relationship where an entity engages in some form of contact, communication, or mutual influence with humans.
-
D.
interactiveElement
Indicates that one entity functions as an interface component designed to receive and respond to user actions initiated by another entity.
-
E.
interactionParadigm
Indicates the general mode or pattern by which entities interact or communicate with each other.
- F. None of above. chosen
Provenance (4 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69fe031af3248190816da6829aef7bab |
completed | May 8, 2026, 3:36 p.m. |
Created at: May 1, 2026, 2:03 a.m.