Triple
T25735477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Fargo (CL-85) |
E645365
|
entity |
| Predicate | nameReassignedTo |
P34101
|
FINISHED |
| Object | USS Fargo (CL-106) |
—
|
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: USS Fargo (CL-106) | Statement: [USS Fargo (CL-85), nameReassignedTo, USS Fargo (CL-106)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameReassignedTo Context triple: [USS Fargo (CL-85), nameReassignedTo, USS Fargo (CL-106)]
-
A.
nameChangeAssociatedWith
Indicates that a change in one entity’s name is linked or correlated with a change or event involving another entity.
-
B.
changedNameOn
Indicates that an entity altered or updated its name at a specific point in time or on a particular date.
-
C.
nameReusedFor
chosen
Indicates that an existing name has been used again for a different entity or instance, rather than introducing a completely new name.
-
D.
changedNameBy
Indicates that one entity altered or updated the name of another entity.
-
E.
changedNameIn
Indicates that an entity has altered or adopted a different name within a specific context, time period, or jurisdiction.
- F. None of above.
Provenance (3 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fcbf71308190a81518c504d5632d |
completed | May 2, 2026, 1:31 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 11:25 p.m.