Triple
T22200192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Kennington |
E548658
|
entity |
| Predicate | usedAsCourtesyOrSubsidiary |
P81246
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Earl of Kennington, usedAsCourtesyOrSubsidiary, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsCourtesyOrSubsidiary Context triple: [Earl of Kennington, usedAsCourtesyOrSubsidiary, yes]
-
A.
usedBySubsidiaryOf
Indicates that something is used by an entity that is a subsidiary of another organization.
-
B.
usedAsCourtesyTitleWithin
Indicates that a term or title is employed as a polite or honorific form of address within a particular context, culture, or setting.
-
C.
hasCourtesyUseBy
Indicates that one entity is permitted to make limited or non-ownership use of another entity as a matter of courtesy.
-
D.
usedVia
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
-
E.
usedAsCourtesyTitleFor
chosen
Indicates that one entity serves as a courtesy title or honorific form of address applied to 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aea51d48190a570cd36c106ab78 |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:36 p.m.