Triple
T13543290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glen Austin |
E323444
|
entity |
| Predicate | nearbyPlace |
P2064
|
FINISHED |
| Object | Carlswald |
E325189
|
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: Carlswald | Statement: [Glen Austin, nearbyPlace, Carlswald]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Carlswald Context triple: [Glen Austin, nearbyPlace, Carlswald]
-
A.
Carlswald
chosen
Carlswald is a residential and commercial suburb located in the Midrand area between Johannesburg and Pretoria in South Africa.
-
B.
Callisburg
Callisburg is a small rural city located in Cooke County in northern Texas, United States.
-
C.
Arzdorf
Arzdorf is a village and district of the municipality of Wachtberg in the Rhein-Sieg-Kreis region of North Rhine-Westphalia, Germany.
-
D.
Lonnerstadt
Lonnerstadt is a small municipality in the Erlangen-Höchstadt district of Bavaria, Germany, known for its rural character and Franconian cultural heritage.
-
E.
Berlinghausen
Berlinghausen is a village within the municipality of Möhnesee in North Rhine-Westphalia, Germany.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafda36248190acabde65a88c5471 |
completed | April 12, 2026, 2:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f76bae316081909e048ead31a9575a |
completed | May 3, 2026, 3:37 p.m. |
Created at: April 9, 2026, 9:45 p.m.