Triple
T13803318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esch-Uelzecht |
E331694
|
entity |
| Predicate | BelvalCurrentUse |
P44109
|
FINISHED |
| Object | university and research district |
—
|
LITERAL 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: university and research district | Statement: [Esch-Uelzecht, BelvalCurrentUse, university and research district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BelvalCurrentUse Context triple: [Esch-Uelzecht, BelvalCurrentUse, university and research district]
-
A.
valleyUsedFor
chosen
Indicates that a valley serves a particular function, purpose, or activity for something or someone.
-
B.
builtNear
Indicates that one entity was constructed at a location geographically close to another entity.
-
C.
buildingUsedBy
Indicates that a particular building is utilized or occupied by a specified entity for some purpose.
-
D.
valleyLocation
Indicates that one entity is located in, at, or within the geographic bounds of a valley relative to another entity or context.
-
E.
valleyKnownFor
Indicates that a particular valley is widely recognized or notable for a specific feature, product, activity, or characteristic.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de026c36108190a7436034a730a261 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.