Triple
T22621454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leopold Park (Ostend) |
E558290
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Leopold |
—
|
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: Leopold | Statement: [Leopold Park (Ostend), namedAfter, Leopold]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leopold Context triple: [Leopold Park (Ostend), namedAfter, Leopold]
-
A.
Leopold
chosen
Leopold is a masculine given name of Germanic origin historically borne by various European rulers, saints, and notable figures.
-
B.
Leopold
Leopold is a residential suburb located within the City of Greater Geelong in Victoria, Australia.
-
C.
Leopold
Leopold is a brand of professional forestry and land-management equipment and tools offered by Xylem Inc.
-
D.
Leopold Gideon
Leopold Gideon is a character in the 1963 romantic thriller film "Charade," involved in the mystery and intrigue surrounding Regina Lampert.
-
E.
Leopold Hermann
Leopold Hermann is a person known primarily as a notable bearer of the surname Hermann.
- 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e39959481909e0ae67379435f95 |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 3 p.m.