Triple
T14775194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Lee of Fareham |
E347240
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Arthur |
E795491
|
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: Arthur | Statement: [Lord Lee of Fareham, givenName, Arthur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Arthur Context triple: [Lord Lee of Fareham, givenName, Arthur]
-
A.
Arthur
Arthur is a long-running animated children's television series that follows the everyday adventures and life lessons of Arthur Read, an anthropomorphic aardvark, and his friends and family.
-
B.
Arthur
Arthur is the given first name of Art Ross, a prominent early 20th-century Canadian ice hockey player, coach, and executive.
-
C.
Arthur
chosen
Arthur is the given name of Arthur Coningham, a notable British Royal Air Force commander during the World Wars.
-
D.
Arthur
Arthur is the given name of Arthur J. Ornitz, an American cinematographer known for his work on several notable films in the mid-20th century.
-
E.
Arthur
Arthur is the reclusive, misunderstood neighbor known as Boo Radley in Harper Lee’s novel "To Kill a Mockingbird."
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec815dd5081909e927911c06b2d66 |
completed | April 14, 2026, 11:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe0cfd26fc81909fba39c8705437ed |
completed | May 8, 2026, 4:19 p.m. |
Created at: April 10, 2026, 1:31 a.m.