Triple
T10435573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brougham Villiers |
E246028
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Villiers |
E246028
|
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: Villiers | Statement: [Brougham Villiers, familyName, Villiers]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Villiers Context triple: [Brougham Villiers, familyName, Villiers]
-
A.
Villiers
Villiers is a Paris Métro station in the 8th and 17th arrondissements, serving as an interchange between lines 2 and 3.
-
B.
Villiers
chosen
Villiers is a prominent English aristocratic surname historically associated with influential political figures and members of the nobility.
-
C.
Brougham Villiers
Brougham Villiers is a notable member of the Villiers family, recognized primarily for his association with the prominent Villiers lineage.
-
D.
Talbot
Talbot is a surname of English and Norman origin, historically associated with several notable families and individuals.
-
E.
Heydon
Heydon is a surname and place name of English origin, associated with various locations and families in the United Kingdom.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea843f1c8190afca4a42bc364468 |
completed | April 7, 2026, 11:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d9881d84588190a9117064a0950ac1 |
completed | April 10, 2026, 11:30 p.m. |
Created at: April 6, 2026, 12:14 p.m.