Triple
T30741728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baronet |
E782707
|
entity |
| Predicate | belongsToStratum |
P196324
|
FINISHED |
| Object | lower nobility |
—
|
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: lower nobility | Statement: [Baronet, belongsToStratum, lower nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToStratum Context triple: [Baronet, belongsToStratum, lower nobility]
-
A.
belongsToStratigraphicUnit
Indicates that one geological feature or object is part of, or contained within, a specific stratigraphic unit in a stratigraphic framework.
-
B.
strataAre
Indicates that one or more entities are classified as geological or structural layers (strata) in relation to something else.
-
C.
containsStrataFrom
Indicates that one geological unit or object includes within it layers or strata originating from another specified source or unit.
-
D.
typeStratum
Indicates that one entity is classified as a geological or conceptual layer or stratum within which the other entity is situated or to which it belongs.
-
E.
hasStratigraphicPosition
Indicates the relative position of one geological layer or unit within a stratigraphic sequence in relation to another.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
| PDg | Predicate description generation | batch_69fe21afdc4c8190913ac4b55a9a5f52 |
completed | May 8, 2026, 5:47 p.m. |
Created at: April 29, 2026, 8:38 p.m.