Triple
T16473597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Offshore Pirate |
E400128
|
entity |
| Predicate | mainCharacter |
P1183
|
FINISHED |
| Object | Carlyle |
E156422
|
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: Carlyle | Statement: [The Offshore Pirate, mainCharacter, Carlyle]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Carlyle Context triple: [The Offshore Pirate, mainCharacter, Carlyle]
-
A.
Carlyle
chosen
Carlyle is a Scottish surname most famously associated with the 19th-century essayist and historian Thomas Carlyle.
-
B.
Bancroft
Bancroft is an English-origin surname borne by various notable figures in politics, academia, and the arts.
-
C.
Trevelyan
Trevelyan is an English surname historically associated with several notable British families, politicians, and literary figures.
-
D.
Dalrymple
Dalrymple is a surname most notably associated with several Scottish nobles, politicians, and writers across history.
-
E.
Erskine
Erskine is a masculine given name of Scottish origin, traditionally used as both a first name and a surname.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32dd266c48190991a1484eb2f7bcc |
completed | April 18, 2026, 7:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a004f5d16008190bd874080e86b8a2f |
completed | May 10, 2026, 9:26 a.m. |
Created at: April 10, 2026, 5:11 a.m.