Triple
T36486574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mini-SAR (Chandrayaan-1) |
E898949
|
entity |
| Predicate | polarizationMode |
P38744
|
FINISHED |
| Object | 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: circular polarization | Statement: [Mini-SAR (Chandrayaan-1), polarizationMode, circular polarization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: polarizationMode Context triple: [Mini-SAR (Chandrayaan-1), polarizationMode, circular polarization]
-
A.
polarizationModes
chosen
Indicates the specific polarization states or configurations associated with a signal, wave, or optical/electromagnetic system.
-
B.
polarizationLevel
Indicates the degree or intensity of polarization present in a given context, such as between opinions, groups, or signals.
-
C.
hasPolarSetting
Indicates that something is configured or oriented according to a polar coordinate or polar reference system.
-
D.
isPolar
Indicates that something possesses a separation of electric charge resulting in distinct positive and negative regions (i.e., has polarity).
-
E.
polarity
Indicates whether the relationship or statement is affirmed (positive) or denied/opposed (negative).
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.