Triple
T38042477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Samuel B. Roberts (FFG-58) |
E949525
|
entity |
| Predicate | namesakeShipNumber |
P189899
|
FINISHED |
| Object | third U.S. Navy ship named USS Samuel B. Roberts |
—
|
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: third U.S. Navy ship named USS Samuel B. Roberts | Statement: [USS Samuel B. Roberts (FFG-58), namesakeShipNumber, third U.S. Navy ship named USS Samuel B. Roberts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namesakeShipNumber Context triple: [USS Samuel B. Roberts (FFG-58), namesakeShipNumber, third U.S. Navy ship named USS Samuel B. Roberts]
-
A.
namesakeShip
Indicates that one entity is a ship that is named after, or serves as the namesake of, another entity.
-
B.
shipName
Indicates the name assigned to a specific ship in the relationship.
-
C.
shipNumber
Indicates the identifying number assigned to a specific ship.
-
D.
shipNumberInNameSeries
Indicates that a ship’s identifying number is part of a sequentially named series of ships.
-
E.
shipNameWith
Indicates that a ship is associated with or identified by a particular name.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fc44c67118819088accfeded7b449e |
completed | May 7, 2026, 7:52 a.m. |
Created at: May 3, 2026, 4:20 p.m.