Triple
T36196866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle between USS Constitution and HMS Java |
E1047150
|
entity |
| Predicate | countryOfOriginOfHMSJava |
P26
|
FINISHED |
| Object | Royal Navy |
E1982
|
NE 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: Royal Navy | Statement: [Battle between USS Constitution and HMS Java, countryOfOriginOfHMSJava, Royal Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfOriginOfHMSJava Context triple: [Battle between USS Constitution and HMS Java, countryOfOriginOfHMSJava, Royal Navy]
-
A.
countryOfOrigin
chosen
Indicates the country from which an entity originally comes or was first produced, created, or established.
-
B.
engineOriginCountry
Indicates the country where an engine was originally designed, manufactured, or first produced.
-
C.
hasLanguageOfOrigin
Indicates that one entity has its origin or source in the language specified by another entity.
-
D.
historicalOriginCountry
Indicates the country from which something originally came or first emerged in a historical context.
-
E.
countryOfOriginOfPopularVersion
Indicates the country from which the most widely known or popular version of something originates.
- F. None of above.
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_69f76e414bdc8190996f15a544220a3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0248062e608190aae1afdae38d2e5a |
completed | May 11, 2026, 9:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a393419746c8190a2f56199d956d8de |
completed | June 22, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_6a02465a0d38819084c3a6813fb943fc |
completed | May 11, 2026, 9:12 p.m. |
Created at: May 3, 2026, 4:08 p.m.