Triple
T12041975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nepomuk |
E286683
|
entity |
| Predicate | recoveredTownStatusIn |
P102909
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Nepomuk, recoveredTownStatusIn, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recoveredTownStatusIn Context triple: [Nepomuk, recoveredTownStatusIn, 18th century]
-
A.
recoveredIn
Indicates that something lost, damaged, or impaired has been restored or regained within a particular context, process, or location.
-
B.
recoveredFrom
Indicates that an entity has returned to a normal or improved state after previously experiencing or being affected by another specified condition, event, or problem.
-
C.
recovered
Indicates that an entity has returned to a previous, healthier, normal, or functional state after a period of loss, damage, illness, or impairment.
-
D.
remainsRecoveredFrom
Indicates that physical remains of an entity have been found and retrieved from a specified source, location, or context.
-
E.
statusAfterRescue
Indicates the condition or state an entity is in following a rescue event or operation.
- F. None of above. chosen
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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bac9e08190aa1a99c835f29542 |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d91006e14081909838412df082f794 |
completed | April 10, 2026, 2:58 p.m. |
Created at: April 8, 2026, 9:47 p.m.