Triple
T10638994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osborne House |
E250667
|
entity |
| Predicate | postRoyalUse |
P95109
|
FINISHED |
| Object | naval training college |
—
|
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: naval training college | Statement: [Osborne House, postRoyalUse, naval training college]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postRoyalUse Context triple: [Osborne House, postRoyalUse, naval training college]
-
A.
royalVariant
Indicates a relationship where one entity is a special or modified version of another that is associated with royalty, nobility, or regal status.
-
B.
postTown
Indicates the town or locality that serves as the postal address destination for a given address or location.
-
C.
postNominalLetters
Indicates that a person is associated with specific letters placed after their name to denote qualifications, honors, or professional affiliations.
-
D.
royalAppointment
Indicates a formal position, role, or honor that has been officially granted to an entity by a monarch or royal authority.
-
E.
patronMonarch
Indicates a relationship where a monarch acts as a patron, providing support, sponsorship, or protection to another party.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dfaf12188190a5774d4d64674653 |
completed | April 8, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69d6dd83b114819098e84dc658e82d7e |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df463ea8819091d6683e476b4f21 |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 9:04 p.m.