Triple
T14462339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smith-Stanley |
E358613
|
entity |
| Predicate | associatedWithNobilityRank |
P67819
|
FINISHED |
| Object | peerage of England |
—
|
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: peerage of England | Statement: [Smith-Stanley, associatedWithNobilityRank, peerage of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithNobilityRank Context triple: [Smith-Stanley, associatedWithNobilityRank, peerage of England]
-
A.
associatedNobleRank
chosen
Indicates that an entity is linked to or holds a particular noble rank or title.
-
B.
associatedWithNobilityConceptually
Indicates a conceptual or symbolic connection between something and nobility, such as aristocratic status, noble qualities, or related social class ideas.
-
C.
associatedNobleTitle
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
-
D.
associatedNobleFamily
Indicates a relationship where an entity is linked or connected to a particular noble family, typically by heritage, allegiance, or formal association.
-
E.
nobleRankAbove
Indicates that one entity holds a higher noble rank or title in a hierarchy than another entity.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91ad67bc81908ecdaa7262f6dc55 |
completed | April 14, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.