Triple
T34683718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Free Imperial City of Biberach |
E890684
|
entity |
| Predicate | lostStatusIn |
P64517
|
FINISHED |
| Object | early 19th century |
—
|
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: early 19th century | Statement: [Free Imperial City of Biberach, lostStatusIn, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostStatusIn Context triple: [Free Imperial City of Biberach, lostStatusIn, early 19th century]
-
A.
lostStatus
Indicates that an entity has transitioned into a state of being lost, missing, or no longer in its expected or intended possession or location.
-
B.
lostStatusReason
Indicates the reason or cause for which something transitioned into a lost or unsuccessful status.
-
C.
lostStatusConfirmedBy
Indicates that the confirmation or verification of an item’s lost status is provided or asserted by a specific agent or source.
-
D.
loserStatus
Indicates that an entity has been judged or designated as the loser in a particular comparison, contest, or evaluative context.
-
E.
lostDuring
chosen
Indicates that something ceased to be in possession or was no longer retained while a particular event, process, or time period was occurring.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7232a16a081909b775efc60b45244 |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.