Triple
T25887520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gereon |
E652231
|
entity |
| Predicate | hasGivenNameBearerType |
P83908
|
FINISHED |
| Object | noble |
—
|
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: noble | Statement: [Gereon, hasGivenNameBearerType, noble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGivenNameBearerType Context triple: [Gereon, hasGivenNameBearerType, noble]
-
A.
hasGivenNameOfBearer
Indicates that a bearer (such as a person or entity) has a specific given (first) name.
-
B.
hasStandardBearer
Indicates that one entity serves as the official flag- or standard-carrier for another entity, typically in a ceremonial, military, or representative capacity.
-
C.
nameBearerType
chosen
Indicates the specific role or capacity in which an entity bears or carries a given name (e.g., as a person, place, organization, or other type of name bearer).
-
D.
hasBearerFullName
Indicates that an entity (the bearer) is associated with a complete personal name string.
-
E.
hasNotableBearersType
Indicates that an entity has notable bearers belonging to a specified type or category.
- 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603446aa88190852cc9bb25f30655 |
completed | May 2, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 8:18 a.m.