Triple
T24925435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Batfish (SS-310) |
E618840
|
entity |
| Predicate | cityOfPreservation |
P157870
|
FINISHED |
| Object | Muskogee |
—
|
NE NERFINISHED |
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: Muskogee | Statement: [USS Batfish (SS-310), cityOfPreservation, Muskogee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityOfPreservation Context triple: [USS Batfish (SS-310), cityOfPreservation, Muskogee]
-
A.
ancientCity
Indicates that the subject is a historically old or long-established city, typically originating from ancient times.
-
B.
cultLocation
Indicates that a cult or religious group is based in, practices in, or is primarily associated with a particular location.
-
C.
cityDepicted
Indicates that a work (such as an image, artwork, or document) visually or representationally depicts a particular city.
-
D.
isCentralMemorialOf
Indicates that something serves as the primary or main commemorative monument or site dedicated to a particular person, event, or group.
-
E.
cityOfReference
Indicates that one entity serves as the primary or official city associated with, or used as a reference point for, another entity.
- 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 18, 2026, 5:29 a.m.