Triple
T22550266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | theory of unparticles |
E557538
|
entity |
| Predicate | canCoupleVia |
P3984
|
FINISHED |
| Object | higher-dimensional operators |
—
|
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: higher-dimensional operators | Statement: [theory of unparticles, canCoupleVia, higher-dimensional operators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canCoupleVia Context triple: [theory of unparticles, canCoupleVia, higher-dimensional operators]
-
A.
canBeConvenedBy
Indicates that an entity (such as a group, body, or meeting) may be formally brought together or assembled by a specified agent or authority.
-
B.
couplesTo
chosen
Indicates that one entity is joined or linked to another in a way that allows interaction, transfer, or mutual influence between them.
-
C.
isPerfectPairing
Indicates that two entities complement each other exceptionally well, forming an ideal or highly compatible combination.
-
D.
canPass
Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
-
E.
canJoin
Indicates that one entity is permitted or able to become a member or participant in another entity or group.
- 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_69e11e59db848190b4272ecd2b690ffd |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f7546c4819099942c86ca522a60 |
completed | April 29, 2026, 1:31 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:52 p.m.