Triple
T13519127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Wessex |
E322846
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | Lord |
E17266
|
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 | Statement: [Lord Wessex, title, Lord]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lord Context triple: [Lord Wessex, title, Lord]
-
A.
Lord
Lord is a reverential title for Jesus Christ, emphasizing his divine authority, sovereignty, and central role in Christian faith and worship.
-
B.
Lord
chosen
A Lord is a noble title in the United Kingdom traditionally associated with membership in the peerage and, in many cases, a seat in the House of Lords.
-
C.
Lord Anyang
Lord Anyang was a nobleman and royal prince of the Warring States–era Zhao kingdom in ancient China, known primarily as a son of King Wuling of Zhao.
-
D.
Lord Strange
Lord Strange is a historic English noble title traditionally held by members of the Stanley family, prominent in late medieval and early modern British politics.
-
E.
Lord's
Lord's is a historic cricket ground in London widely regarded as the "Home of Cricket" and a premier venue for major international matches.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafa27f048190bed33a98e28c8d09 |
completed | April 12, 2026, 2:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f75498153c819096a28a7f0b608ff5 |
completed | May 3, 2026, 1:58 p.m. |
Created at: April 9, 2026, 9:44 p.m.