Triple
T24811102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poincaré sphere |
E620788
|
entity |
| Predicate | bottomPointRepresents |
P157360
|
FINISHED |
| Object | right-handed 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: right-handed circular polarization | Statement: [Poincaré sphere, bottomPointRepresents, right-handed circular polarization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bottomPointRepresents Context triple: [Poincaré sphere, bottomPointRepresents, right-handed circular polarization]
-
A.
lowestPoint
Indicates that one entity is the point with the minimum vertical position or value relative to another entity or within a specified context.
-
B.
lowestPointsNear
Indicates that one entity identifies or specifies the locations of the lowest points in elevation or value in the vicinity of another entity.
-
C.
bottomType
Indicates that the subject entity is classified as a bottom-level or most specific type within a type hierarchy.
-
D.
lowerBoundaryLocation
Indicates the place or region where the lower or bottom boundary of something is situated.
-
E.
liesBelow
Indicates that one entity is positioned at a lower vertical level than another entity.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f42b11251881908070b93355de64ad |
completed | May 1, 2026, 4:24 a.m. |
Created at: April 18, 2026, 4:50 a.m.