Triple
T6780560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon Spoor |
E155669
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Spoor |
E605438
|
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: Spoor | Statement: [Simon Spoor, familyName, Spoor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Spoor Context triple: [Simon Spoor, familyName, Spoor]
-
A.
Spoor
chosen
Spoor is a Dutch surname most notably borne by Simon Hendrik Spoor, a prominent military leader in the mid-20th century.
-
B.
Heenweg
Heenweg is a small village in the Dutch municipality of Westland in the province of South Holland, Netherlands.
-
C.
Spoornet
Spoornet was South Africa’s former state-owned freight rail operator, responsible for much of the country’s heavy rail transport before being restructured and rebranded.
-
D.
Driewegen
Driewegen is a small village in the Dutch province of Zeeland, located within the municipality of Borsele.
-
E.
Heenvliet
Heenvliet is a small historic town in the western Netherlands, known for its medieval castle ruins and rural setting within the province of South Holland.
- 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d26b32c0819093f86b1002260660 |
completed | March 27, 2026, 6:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c712d27a388190ab44e6e754019fca |
completed | March 27, 2026, 11:29 p.m. |
Created at: March 27, 2026, 2:14 p.m.