Triple
T26601633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French warship Pélican |
E667649
|
entity |
| Predicate | roleInBattleOfHudsonBay |
P101544
|
FINISHED |
| Object | defeated English squadron |
—
|
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: defeated English squadron | Statement: [French warship Pélican, roleInBattleOfHudsonBay, defeated English squadron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBattleOfHudsonBay Context triple: [French warship Pélican, roleInBattleOfHudsonBay, defeated English squadron]
-
A.
roleInBankOfNorthAmerica
Indicates that an entity holds or held a specific role or position within the Bank of North America.
-
B.
roleInColonies
Indicates the specific function, position, or responsibility an entity holds within one or more colonies.
-
C.
roleInBattleOfHubbardton
chosen
Indicates the specific role or involvement an entity had in the Battle of Hubbardton.
-
D.
roleInManchuria
Indicates that an entity holds or held a specific role, position, or function in the context of Manchuria.
-
E.
foundedAsTradingPostBy
Indicates that an entity was originally established as a trading post by a specified founder or founding group.
- 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_69ee9cfd20348190bb1255d2603efb7a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 27, 2026, 2:12 a.m.