Triple
T14445223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Ranger |
E358187
|
entity |
| Predicate | nameNumberInUSN |
P114309
|
FINISHED |
| Object | fourth U.S. Navy ship named Ranger |
—
|
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: fourth U.S. Navy ship named Ranger | Statement: [USS Ranger, nameNumberInUSN, fourth U.S. Navy ship named Ranger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameNumberInUSN Context triple: [USS Ranger, nameNumberInUSN, fourth U.S. Navy ship named Ranger]
-
A.
numberOfNames
Indicates the count of distinct names associated with a given entity.
-
B.
testNumberInUSProgram
Indicates that a given test number is included in, or associated with, a specific program in the United States.
-
C.
nameElementIn
Indicates that an entity is (or contains) a specific name element within a larger naming structure or system.
-
D.
namesakeStatus
Indicates that one entity serves as the namesake of another, or that two entities share a relationship based on having the same name.
-
E.
SSNumber
Indicates that an entity has a specific Social Security Number assigned to it.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de915e76f481909fe9462f964b5b1c |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:19 a.m.