Triple
T3070738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal St George’s Golf Club |
E64012
|
entity |
| Predicate | hasRoyalStatus |
P44258
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Royal St George’s Golf Club, hasRoyalStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoyalStatus Context triple: [Royal St George’s Golf Club, hasRoyalStatus, true]
-
A.
hasRoyalConnection
Indicates a relationship where an entity is linked or associated in some notable way to royalty, a royal family, or a royal institution.
-
B.
isRoyalTitle
Indicates that something is a formal title associated with royalty or a royal rank.
-
C.
hasRoyalHouse
Indicates that an entity is associated with or belongs to a particular royal house or dynasty.
-
D.
legalStatusOfMonarch
Indicates the legal status or standing that a monarch holds within a given legal or constitutional framework.
-
E.
hasRoyalWarrantFrom
Indicates that one party has been formally granted a royal warrant or official endorsement by a specific royal person or household.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada14b366881908e2ca104e5f38251 |
completed | March 8, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69ad9625b30c819099ef9349c91d7b25 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f7630c81908e1ca8a69611cff6 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3:02 p.m.