Triple
T36127676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Key West (SSN-722) |
E1044926
|
entity |
| Predicate | locationNamedFor |
P204754
|
FINISHED |
| Object | Florida |
E549
|
NE 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: Florida | Statement: [USS Key West (SSN-722), locationNamedFor, Florida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationNamedFor Context triple: [USS Key West (SSN-722), locationNamedFor, Florida]
-
A.
locationSymbolic
Indicates a symbolic or abstract locational relationship between entities, where one is associated with a place or position in a non-literal, representational, or conceptual sense.
-
B.
locationFound
Indicates that a particular entity is located or discovered at a specific place or position.
-
C.
namedForCity
Indicates that one entity is named after, or derives its name from, a particular city.
-
D.
locationFormed
Indicates the place or geographic area where an entity (such as an organization, group, or structure) was originally established or came into existence.
-
E.
locates
Indicates that one entity determines, specifies, or identifies the position or place of another entity in space or within a given context.
- F. None of above. chosen
Provenance (5 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38ddf2aa888190b40731f505cdb519 |
completed | June 22, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:08 p.m.