Triple
T30931306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lords of Castro |
E787998
|
entity |
| Predicate | postElevationStatus |
P60297
|
FINISHED |
| Object | duchy |
—
|
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: duchy | Statement: [Lords of Castro, postElevationStatus, duchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postElevationStatus Context triple: [Lords of Castro, postElevationStatus, duchy]
-
A.
post-elevationRank
chosen
Indicates that one entity holds a higher or later elevation-based rank or status than another entity.
-
B.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
C.
elevationBy
Indicates a relationship where one entity raises, increases, or enhances the level, status, or intensity of another entity.
-
D.
elevationConnection
Indicates a relationship where one entity is linked to another through a change or difference in elevation, such as a vertical or sloped connection between their heights or levels.
-
E.
elevationResultedIn
Indicates that a change in elevation of one entity caused or led to a particular outcome or effect in another context or entity.
- 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f692e0fae88190a9d50929f33dd365 |
completed | May 3, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:52 p.m.