Triple
T24671430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bon Homme Richard |
E610844
|
entity |
| Predicate | wasOriginalNameFor |
P104716
|
FINISHED |
| Object | USS Yorktown (CV-10) |
—
|
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 Yorktown (CV-10) | Statement: [Bon Homme Richard, wasOriginalNameFor, USS Yorktown (CV-10)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasOriginalNameFor Context triple: [Bon Homme Richard, wasOriginalNameFor, USS Yorktown (CV-10)]
-
A.
hasOriginalNameOf
chosen
Indicates that one entity is the original or earlier name from which another entity’s current or later name is derived.
-
B.
wasOriginally
Indicates that an entity had a particular state, form, type, or affiliation at an earlier time, which has since changed.
-
C.
hasUncertainOriginalName
Indicates that the entity’s original name is not known with certainty or is subject to doubt or ambiguity.
-
D.
wasRenamedBackTo
Indicates that an entity, after having its name changed, was later restored to its previous or original name.
-
E.
originalFor
Indicates that one entity serves as the source, basis, or prototype from which another entity is derived, adapted, or created.
- 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_69e2c4d505cc8190981881df06c0bf52 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:42 a.m.