Triple
T6840720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulrich |
E157565
|
entity |
| Predicate | hasHistoricalBearerType |
P42372
|
FINISHED |
| Object | nobles |
—
|
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: nobles | Statement: [Ulrich, hasHistoricalBearerType, nobles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalBearerType Context triple: [Ulrich, hasHistoricalBearerType, nobles]
-
A.
hasHistoricalBearer
Indicates that an entity has, at some point in history, been borne or carried by another entity (such as a person, group, or institution).
-
B.
hasPrimaryBearer
Indicates that one entity serves as the main or principal holder, carrier, or possessor of another entity.
-
C.
hasNotableBearersType
chosen
Indicates that an entity has notable bearers belonging to a specified type or category.
-
D.
hasStandardBearer
Indicates that one entity serves as the official flag- or standard-carrier for another entity, typically in a ceremonial, military, or representative capacity.
-
E.
hasTypeHistory
Indicates that an entity is associated with a record or sequence of its past and present types or classifications over time.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d6b4a1f88190b4f532828697fbd8 |
completed | March 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:19 p.m.