Triple
T22854363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philips van Almonde |
E566438
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | van Almonde |
—
|
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: van Almonde | Statement: [Philips van Almonde, familyName, van Almonde]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: van Almonde Context triple: [Philips van Almonde, familyName, van Almonde]
-
A.
van Almonde
chosen
Van Almonde is a Dutch noble family name most notably associated with Admiral Philips van Almonde, a prominent naval commander of the 17th-century Dutch Republic.
-
B.
van Egmond
Van Egmond is a Dutch noble family name historically associated with influential aristocratic lineages in the Netherlands.
-
C.
van Alphen
Van Alphen is a Dutch surname associated with various notable individuals in fields such as science, literature, and public life.
-
D.
van Amsberg
Van Amsberg is the German-origin noble family name associated with the Dutch royal family, including members such as Prince Constantijn of the Netherlands.
-
E.
van Berkel
van Berkel is a Dutch surname most notably associated with architect Ben van Berkel, co-founder of the architecture firm UNStudio.
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17ebb4ea48190b4b865e316f6a75f |
completed | April 29, 2026, 3:44 a.m. |
Created at: April 17, 2026, 3:37 p.m.