Triple
T38561225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warmbronn |
E928079
|
entity |
| Predicate | hasNotablePersonDeathPlace |
P26600
|
FINISHED |
| Object | Frei Otto |
E271805
|
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: Frei Otto | Statement: [Warmbronn, hasNotablePersonDeathPlace, Frei Otto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePersonDeathPlace Context triple: [Warmbronn, hasNotablePersonDeathPlace, Frei Otto]
-
A.
notablePersonDiedHere
chosen
Indicates that a notable or famous person died at the referenced location.
-
B.
hasNotablePersonBornHere
Indicates that a notable or distinguished person was born at the referenced place.
-
C.
hasHonoureePlaceOfDeath
Indicates the place where the honoured person died.
-
D.
hasNotablePersonRaisedHere
Indicates that a notable person spent their formative or upbringing years in the referenced place.
-
E.
isBorneByNotablePeopleIn
Indicates that something (such as a name, title, or attribute) is carried or held by notable people within a specified place or context.
- F. None of above.
Provenance (4 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41e04369548190b5115a4868ed1cb6 |
completed | June 29, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.