Triple
T9593829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAMPSON radar |
E231481
|
entity |
| Predicate | scanDimension |
P35105
|
FINISHED |
| Object | azimuth |
—
|
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: azimuth | Statement: [SAMPSON radar, scanDimension, azimuth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scanDimension Context triple: [SAMPSON radar, scanDimension, azimuth]
-
A.
dimensionOfCurrent
Indicates the dimensional property (such as magnitude or units) associated with the current in a given context.
-
B.
scanDirection
chosen
Indicates the direction or orientation in which a scanning action is performed or data is acquired.
-
C.
graphicsDimension
Indicates a relationship where an entity has or is associated with a specific graphical size or dimensional properties.
-
D.
includesDimension
Indicates that one entity encompasses or contains a particular dimension or measurable aspect as part of its definition or structure.
-
E.
hasIndividualDimension
Indicates that an entity possesses a specific, separately identifiable dimension or measurable extent as an individual attribute.
- 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_69ca8482884481908eccdfdf64d6fbf7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a134b0c81908a568e5d2ecfbb92 |
completed | April 1, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a359788190b24f82399489f7fe |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:07 p.m.