Triple
T31117231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lordship of Hanau |
E793122
|
entity |
| Predicate | eventualElevation |
P3787
|
FINISHED |
| Object | county |
—
|
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: county | Statement: [Lordship of Hanau, eventualElevation, county]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventualElevation Context triple: [Lordship of Hanau, eventualElevation, county]
-
A.
elevatedTo
chosen
Indicates that one entity is promoted or raised to a higher rank, status, position, or level relative to another.
-
B.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
C.
elevationHolder
Indicates that one entity serves as the reference or container for the elevation (height above a baseline) associated with another entity.
-
D.
elevationResultedIn
Indicates that a change in elevation of one entity caused or led to a particular outcome or effect in another context or entity.
-
E.
elevatedFeature
Indicates that one feature or element is positioned or raised higher relative to another reference level or surrounding 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 29, 2026, 9:04 p.m.