Triple
T26765541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Σ*(1385) |
E674926
|
entity |
| Predicate | isSubjectToInteraction |
P1313
|
FINISHED |
| Object | strong interaction |
—
|
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: strong interaction | Statement: [Σ*(1385), isSubjectToInteraction, strong interaction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubjectToInteraction Context triple: [Σ*(1385), isSubjectToInteraction, strong interaction]
-
A.
isSubjectTo
chosen
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
-
B.
hasInteraction
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
C.
hasInteractionEffects
Indicates that one entity’s presence, action, or state alters, influences, or modifies the behavior, effect, or outcome associated with another entity.
-
D.
specifiesInteractionWith
Indicates that one entity defines or determines the type, parameters, or nature of interaction it has with another entity.
-
E.
selfInteracts
Indicates that an entity interacts with itself, rather than with a distinct external entity.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 3:59 a.m.