Triple
T13803317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esch-Uelzecht |
E331694
|
entity |
| Predicate | BelvalFormerUse |
P44099
|
FINISHED |
| Object | steelworks site |
—
|
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: steelworks site | Statement: [Esch-Uelzecht, BelvalFormerUse, steelworks site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BelvalFormerUse Context triple: [Esch-Uelzecht, BelvalFormerUse, steelworks site]
-
A.
previousBuildingUse
Indicates that a building previously served a specified use or function before its current one.
-
B.
formerLandUse
chosen
Indicates the type of land use that characterized a location prior to its current or present use.
-
C.
valleyUsedFor
Indicates that a valley serves a particular function, purpose, or activity for something or someone.
-
D.
buildingUsedBy
Indicates that a particular building is utilized or occupied by a specified entity for some purpose.
-
E.
occupiesFormerBuilding
Indicates that one entity is currently using or located in a building that was previously used or occupied by another entity.
- 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.