Triple
T963926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Bonhomme Richard |
E20793
|
entity |
| Predicate | crewNationality |
P14610
|
FINISHED |
| Object | multinational crew |
—
|
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: multinational crew | Statement: [USS Bonhomme Richard, crewNationality, multinational crew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewNationality Context triple: [USS Bonhomme Richard, crewNationality, multinational crew]
-
A.
namedForNationality
Indicates that something is named after or in reference to a particular nationality or national identity.
-
B.
nationalityRepresented
Indicates the country or nation that an entity officially represents, typically in a professional, competitive, or diplomatic capacity.
-
C.
sponsorNationality
Indicates that an entity acts as a sponsor and has the specified nationality.
-
D.
brandNationality
Indicates that a brand is associated with or originates from a particular country or nationality.
-
E.
nationalityOfPersonnel
chosen
Indicates the country or countries to which the personnel involved in an activity, organization, or context belong by citizenship or national affiliation.
- 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_69a493b21f2881908132dcf45dcd2f36 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b4303e5881909d101d11f9732c75 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a2e23c8190b932fe88b02f995d |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.