Triple
T10389265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weil pairing |
E244846
|
entity |
| Predicate | isPerfectPairing |
P93942
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Weil pairing, isPerfectPairing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPerfectPairing Context triple: [Weil pairing, isPerfectPairing, true]
-
A.
isPairOf
Indicates that two entities are associated as a matched or corresponding pair within a defined context.
-
B.
isPerfect
Indicates that an entity possesses all required qualities or characteristics to the highest or complete degree, without flaws or deficiencies.
-
C.
starPairing
Indicates a relationship where two stars are associated or grouped together as a pair, typically for observational, analytical, or classificatory purposes.
-
D.
commonPair
Indicates that two entities commonly occur together or are frequently associated as a pair in some shared context.
-
E.
dualPair
Indicates that two entities form a dual pair, standing in a mathematically defined dual relationship where each is the dual counterpart of the 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9b40dd8819080ac839487020a44 |
completed | April 7, 2026, 11:25 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb0e7a88190bec0b7a52c70dfe2 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:05 p.m.