Triple
T37668534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wriothesley |
E937885
|
entity |
| Predicate | hasTypicalBearersClass |
P34346
|
FINISHED |
| Object | 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: nobility | Statement: [Wriothesley, hasTypicalBearersClass, nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalBearersClass Context triple: [Wriothesley, hasTypicalBearersClass, nobility]
-
A.
typicalBearers
chosen
Indicates that certain entities are the usual or characteristic holders, users, or possessors of a given property, role, or attribute.
-
B.
hasNotableBearersType
Indicates that an entity has notable bearers belonging to a specified type or category.
-
C.
hasMultipleBearers
Indicates that a single item, attribute, or role is associated with more than one bearer or holder simultaneously.
-
D.
hasPrimaryBearer
Indicates that one entity serves as the main or principal holder, carrier, or possessor of another entity.
-
E.
intendedBearers
Indicates the entities for whom something (such as a role, attribute, or responsibility) is meant to apply or be held.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fff09dae088190bd8460060d778feb |
completed | May 10, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69fff0027c5c8190baa5c7a15852cbe0 |
completed | May 10, 2026, 2:40 a.m. |
Created at: May 3, 2026, 4:18 p.m.