Triple
T24658331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herzog von Geldern |
E610458
|
entity |
| Predicate | importantResidence |
P75
|
FINISHED |
| Object | Nijmegen |
—
|
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: Nijmegen | Statement: [Herzog von Geldern, importantResidence, Nijmegen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importantResidence Context triple: [Herzog von Geldern, importantResidence, Nijmegen]
-
A.
residence
chosen
Indicates that one entity lives at, is based in, or habitually occupies the location represented by the other entity.
-
B.
ownedResidence
Indicates that one entity has ownership of a dwelling or place of residence associated with another entity.
-
C.
inResidenceAt
Indicates that an entity lives or resides at a particular location or residence.
-
D.
builtResidence
Indicates that one entity constructed or was responsible for constructing a residence for another entity or for itself.
-
E.
otherResidence
Indicates that an entity has an additional or alternative place of residence beyond its primary home.
- F. None of above.
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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 2:34 a.m.