Triple
T2841430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bognor Regis |
E62477
|
entity |
| Predicate | honorificIndicates |
P42968
|
FINISHED |
| Object | royal connection |
—
|
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: royal connection | Statement: [Bognor Regis, honorificIndicates, royal connection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificIndicates Context triple: [Bognor Regis, honorificIndicates, royal connection]
-
A.
honorificSense
Indicates that one entity refers to another using an honorific or respectful linguistic form.
-
B.
honorificType
Indicates the type or category of honorific or formal title associated with an entity in a given context.
-
C.
isHonorific
Indicates that one entity functions as an honorific title or respectful form of address applied to another entity.
-
D.
honorificPrefix
Indicates the formal title or respectful prefix (e.g., "Dr.", "Mr.", "Prof.") used before a person's name to denote status, role, or honor.
-
E.
honorificUsage
Indicates that one entity refers to or addresses another using an honorific title or respectful linguistic form.
- F. None of above. chosen
Provenance (4 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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf16d0c08190bb8de4a4160b4414 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd0ce8b08190ba28c192988f38ce |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde4895dc819097c396c5d31ac1d1 |
completed | March 7, 2026, 8:14 a.m. |
Created at: March 6, 2026, 10:01 p.m.