Triple
T22595724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brandon deWilde |
E574674
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | deWilde |
—
|
NE NERFINISHED |
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: deWilde | Statement: [Brandon deWilde, familyName, deWilde]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: deWilde Context triple: [Brandon deWilde, familyName, deWilde]
-
A.
deWilde
chosen
deWilde is a surname most notably associated with American child actor Brandon deWilde, known for his roles in classic mid-20th-century films.
-
B.
Wilda
Wilda is a district of the Polish city of Poznań, known for its mix of historic architecture, industrial heritage, and growing residential and cultural areas.
-
C.
Du Welz
Du Welz is the surname of Belgian film director and screenwriter Fabrice Du Welz, known for his intense and atmospheric genre films.
-
D.
Veeweyde
Veeweyde is a neighborhood-level district within the Brussels municipality of Anderlecht, known primarily as a residential area served by the Veeweyde metro station.
-
E.
Willerd
Willerd is a less common variant spelling of the given name Willard, typically used as a masculine first name.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f16268cb54819084a0f27ec0473f35 |
completed | April 29, 2026, 1:44 a.m. |
Created at: April 17, 2026, 2:49 p.m.