Triple
T30931305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lords of Castro |
E787998
|
entity |
| Predicate | preElevationStatus |
P170314
|
FINISHED |
| Object | lordship |
—
|
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: lordship | Statement: [Lords of Castro, preElevationStatus, lordship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preElevationStatus Context triple: [Lords of Castro, preElevationStatus, lordship]
-
A.
preSubmergenceElevation
Indicates the elevation or height of something before it becomes submerged or covered by water.
-
B.
elevationBeforeCollapse
Indicates that one entity’s elevation value is measured or defined as it was prior to a collapse event affecting that entity or its supporting structure.
-
C.
elevationDeterminedIn
Indicates that the elevation of an entity is established or measured within a specific context, process, or event.
-
D.
elevationChange
Indicates a change in vertical position or altitude between two points or states.
-
E.
elevationHolder
Indicates that one entity serves as the reference or container for the elevation (height above a baseline) associated with another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69f68c517f308190873c1c7e05a0c6d0 |
completed | May 2, 2026, 11:44 p.m. |
Created at: April 29, 2026, 8:52 p.m.