Triple
T11333667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellen Bowen |
E268411
|
entity |
| Predicate | hasRomanticInterestIn |
P7325
|
FINISHED |
| Object | Lord John Brindale |
E224429
|
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: Lord John Brindale | Statement: [Ellen Bowen, hasRomanticInterestIn, Lord John Brindale]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lord John Brindale Context triple: [Ellen Bowen, hasRomanticInterestIn, Lord John Brindale]
-
A.
Lord John Brindale
chosen
Lord John Brindale is a fictional aristocratic suitor featured in the 1951 romantic comedy film "Royal Wedding."
-
B.
Edmund Brock
Edmund Brock is a person notable enough to be recognized as a distinguished bearer of the surname Brock.
-
C.
Richard Bellingham
Richard Bellingham was a 17th-century colonial magistrate and politician who served multiple terms as governor of the Massachusetts Bay Colony.
-
D.
Lord Danvers
Lord Danvers is a fictional nobleman appearing as a character in William Godwin’s novel "Cloudesley."
-
E.
Peregrine Maitland
Peregrine Maitland was a British army officer and colonial administrator who served in several key imperial posts in the early 19th century.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9fe5d5881908d786b212a554d8b |
completed | April 9, 2026, 6:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5263160548190adb7d5c0fd6af0e2 |
completed | April 19, 2026, 7 p.m. |
Created at: April 8, 2026, 9:33 p.m.