Triple
T25815711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Shannon |
E650242
|
entity |
| Predicate | hasCaptainDuringWarOf1812 |
P115062
|
FINISHED |
| Object | Philip Broke |
—
|
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: Philip Broke | Statement: [HMS Shannon, hasCaptainDuringWarOf1812, Philip Broke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaptainDuringWarOf1812 Context triple: [HMS Shannon, hasCaptainDuringWarOf1812, Philip Broke]
-
A.
captainServedUnder
Indicates that one captain performed their service or held their position under the authority or command of another person.
-
B.
positionOnWarOf1812
Indicates a stance, opinion, or alignment that an entity holds regarding the War of 1812.
-
C.
notableCommanderAmerican
Indicates that the subject served as a notable military commander who is American.
-
D.
servedAsCaptainFrom
chosen
Indicates that an entity held the role of captain of another entity starting from a specified point in time.
-
E.
hasAlliedLeader
Indicates that one entity serves as an allied leader or commander in relation to another entity.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 22, 2026, 7:26 a.m.