Triple
T6545719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan van Galen |
E151001
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | van Galen |
E151001
|
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: van Galen | Statement: [Jan van Galen, familyName, van Galen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: van Galen Context triple: [Jan van Galen, familyName, van Galen]
-
A.
van Wijnbergen
Van Wijnbergen is a Dutch surname associated with individuals such as Everdine Huberta van Wijnbergen.
-
B.
van Slingelandt
Van Slingelandt is a Dutch surname historically associated with a prominent political and administrative family in the Netherlands.
-
C.
Goudriaan
Goudriaan is a small village in the Dutch province of South Holland, known for its rural character and historic polder landscape.
-
D.
Jan van Galen
chosen
Jan van Galen was a 17th-century Dutch naval officer and admiral known for his role in the Anglo-Dutch Wars.
-
E.
van Egeraat
van Egeraat is a Dutch surname most prominently associated with architect Erik van Egeraat.
- 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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6adee47cc8190830dbc1228b788ee |
completed | March 27, 2026, 4:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6d54814848190bc397d9b81abc042 |
completed | March 27, 2026, 7:06 p.m. |
Created at: March 27, 2026, 1:50 p.m.