Triple
T795894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dyson’s transform |
E17018
|
entity |
| Predicate | methodType |
P859
|
FINISHED |
| Object | bijective technique |
—
|
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: bijective technique | Statement: [Dyson’s transform, methodType, bijective technique]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodType Context triple: [Dyson’s transform, methodType, bijective technique]
-
A.
method
chosen
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
-
B.
codeType
Indicates the classification or category assigned to a particular code within a coding or encoding system.
-
C.
argumentType
Indicates that one entity serves as a specific semantic or syntactic argument role (such as subject, object, or complement) in relation to another entity or event.
-
D.
propagationMethod
Indicates the means or mechanism by which something spreads, reproduces, or is transmitted from one entity or location to another.
-
E.
typeOfOperation
Indicates the specific kind or category of operation being performed or referenced in a given 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a7b172e88190a26d31c9075b81fb |
completed | March 1, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69a4a510f61881909175d6d8719246cd |
completed | March 1, 2026, 8:44 p.m. |
Created at: March 1, 2026, 7:38 p.m.