Triple
T8031687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leuna |
E186997
|
entity |
| Predicate | wasMajorSiteFor |
P7849
|
FINISHED |
| Object | synthetic fuel production |
—
|
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: synthetic fuel production | Statement: [Leuna, wasMajorSiteFor, synthetic fuel production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMajorSiteFor Context triple: [Leuna, wasMajorSiteFor, synthetic fuel production]
-
A.
isSiteOf
chosen
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
B.
bestKnownAsSiteOf
Indicates that a place is most widely recognized or famous for being the location where a particular event, activity, or feature occurs or is found.
-
C.
notableSiteAssociatedWith
Indicates that there is a significant or noteworthy site or location that is associated with, related to, or prominently linked to the given entity.
-
D.
formerSiteOf
Indicates that a location previously hosted or contained something (such as a structure, organization, or event) that is no longer present there.
-
E.
notableSite
Indicates that a site holds particular significance, prominence, or recognition in some context.
- 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_69ca82ae2d1081909dbfee42b41db419 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3eef921081908d0ea21f142c175a |
completed | March 31, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69cb049688208190b32088bd2c5930bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:22 p.m.