Triple
T2070946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 45 destroyer |
E44813
|
entity |
| Predicate | hasSonar |
P17204
|
FINISHED |
| Object | bow-mounted sonar |
—
|
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: bow-mounted sonar | Statement: [Type 45 destroyer, hasSonar, bow-mounted sonar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSonar Context triple: [Type 45 destroyer, hasSonar, bow-mounted sonar]
-
A.
hasSensor
chosen
Indicates that one entity is equipped with, contains, or uses a particular sensor.
-
B.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
C.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
D.
hasDunes
Indicates that one entity (typically a geographic area or surface) possesses or is characterized by sand dunes.
-
E.
hasHeavierSoundThan
Indicates that one entity produces or is associated with a sound that is sonically heavier, more intense, or more forceful than that of another entity.
- 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_69a88916c2b48190a5ca2e9b12cad3ed |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba0d20bc8190b19a32157f8b1607 |
completed | March 7, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69abb7b0edac8190a58eabee55f73deb |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.