Triple
T24810978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jones calculus |
E620785
|
entity |
| Predicate | commonBasis |
P158117
|
FINISHED |
| Object | left and right circular polarization |
—
|
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: left and right circular polarization | Statement: [Jones calculus, commonBasis, left and right circular polarization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonBasis Context triple: [Jones calculus, commonBasis, left and right circular polarization]
-
A.
commonBasis
chosen
Indicates that two or more entities share an underlying foundation, principle, or set of assumptions that supports or explains their relationship.
-
B.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
C.
sharesCommonAncestorWith
Indicates that two entities have at least one ancestor in common in their lineage or hierarchy.
-
D.
commonFor
Indicates that something is typical, usual, or frequently occurring for a given entity or context.
-
E.
commonOn
Indicates that two or more entities share the same location, context, or medium where they are present or occur together.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 4:50 a.m.