Triple
T2372793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RADARSAT-2 |
E46127
|
entity |
| Predicate | polarizationModes |
P38744
|
FINISHED |
| Object | single 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: single polarization | Statement: [RADARSAT-2, polarizationModes, single polarization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: polarizationModes Context triple: [RADARSAT-2, polarizationModes, single polarization]
-
A.
polarity
Indicates whether the relationship or statement is affirmed (positive) or denied/opposed (negative).
-
B.
electricalPolarity
Indicates that there is a relationship specifying the direction or type of electrical charge or potential difference associated with an entity or connection.
-
C.
logicalPolarity
Indicates that the truth value of a statement is affirmed (positive) or denied (negative) relative to some logical context.
-
D.
signalPolarity
Indicates the directional orientation or sign (positive or negative) of a signal relative to a defined reference.
-
E.
displayMode
Indicates how content or information is visually presented or arranged to the user.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abca4d89248190be7d712d5fa8382b |
completed | March 7, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69abc59d82f08190b7c36982d1ae783d |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abca4c937c8190b4dfca716b868d4f |
completed | March 7, 2026, 6:48 a.m. |
Created at: March 4, 2026, 7:56 p.m.