Triple
T30377752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Cyane |
E772737
|
entity |
| Predicate | originalCountryOfOrigin |
P26
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [USS Cyane, originalCountryOfOrigin, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalCountryOfOrigin Context triple: [USS Cyane, originalCountryOfOrigin, United Kingdom]
-
A.
countryOfOrigin
chosen
Indicates the country from which an entity originally comes or was first produced, created, or established.
-
B.
formerCountryOfOrigin
Indicates that an entity was previously the country from which another entity originated, but is no longer its current country of origin.
-
C.
laterCountryOfOrigin
Indicates that an entity’s country of origin changed, and this predicate specifies the country that became its origin at a later time than a previously associated country.
-
D.
parentCountryOfOrigin
Indicates that one country is the original source or homeland from which another country historically emerged or originated.
-
E.
organizationCountryOfOrigin
Indicates the country where an organization was originally founded or established.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00332eaa0c8190a69ea895576bb0ee |
completed | May 10, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_6a0032b2ea80819083b89ebb88165933 |
completed | May 10, 2026, 7:24 a.m. |
Created at: April 29, 2026, 8 p.m.