Triple
T15597684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount Coke |
E374947
|
entity |
| Predicate | courtesyUsage |
P81246
|
FINISHED |
| Object | customary for heir apparent |
—
|
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: customary for heir apparent | Statement: [Viscount Coke, courtesyUsage, customary for heir apparent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtesyUsage Context triple: [Viscount Coke, courtesyUsage, customary for heir apparent]
-
A.
hasCourtesyUseBy
Indicates that one entity is permitted to make limited or non-ownership use of another entity as a matter of courtesy.
-
B.
usedAsCourtesyTitleFor
chosen
Indicates that one entity serves as a courtesy title or honorific form of address applied to another entity.
-
C.
eligibleUses
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
-
D.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
E.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
- 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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e609ab081909feb486a57439960 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:12 a.m.