Triple
T24811105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poincaré sphere |
E620788
|
entity |
| Predicate | pointOnSphereRepresents |
P95762
|
FINISHED |
| Object | a unique polarization state |
—
|
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: a unique polarization state | Statement: [Poincaré sphere, pointOnSphereRepresents, a unique polarization state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointOnSphereRepresents Context triple: [Poincaré sphere, pointOnSphereRepresents, a unique polarization state]
-
A.
starPointRepresents
Indicates that a specific star point symbol or marker is used to represent or denote another entity, feature, or value.
-
B.
სფერო
Indicates a general field, domain, or area within which something operates, applies, or is categorized.
-
C.
positionOnCityCircle
Indicates that one entity is located along the circular boundary or ring-shaped layout defined by a city.
-
D.
KPoint
Indicates a relationship where a specific point is designated or identified as a key or reference point within a spatial or geometric context.
-
E.
representsPositionOn
chosen
Indicates that one entity specifies or defines the spatial or logical position of another entity within 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_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. |
Created at: April 18, 2026, 4:50 a.m.