Triple
T156359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milwaukee Deep |
E3189
|
entity |
| Predicate | discoveryMethod |
P7311
|
FINISHED |
| Object | sounding |
—
|
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: sounding | Statement: [Milwaukee Deep, discoveryMethod, sounding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryMethod Context triple: [Milwaukee Deep, discoveryMethod, sounding]
-
A.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
B.
hasDiscoveryFacility
Indicates that an entity has, is associated with, or is served by a facility where discoveries (such as scientific, medical, or technological findings) are made or were made.
-
C.
discoveredBy
Indicates that something was found, identified, or brought to light through the efforts or actions of a particular agent.
-
D.
discoveryDate
Indicates the date on which something was first discovered or identified.
-
E.
wasDiscoveredIn
Indicates that an entity became known or was first identified during a specific time period or at a particular place.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a2565ded588190a27319aaa0130b4f |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2587e598c81909e1082b813971f48 |
completed | Feb. 28, 2026, 2:52 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.