Triple
T17741997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief Secretary to the Admiralty |
E442881
|
entity |
| Predicate | isHistoricOccupation |
P107616
|
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: [Chief Secretary to the Admiralty, isHistoricOccupation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricOccupation Context triple: [Chief Secretary to the Admiralty, isHistoricOccupation, true]
-
A.
hasHistoricalOccupationTool
Indicates that an entity historically used or was associated with a particular tool in the context of its occupation or trade.
-
B.
hasHistoricalOccupationMaterial
Indicates that something is composed of or contains material evidence related to past occupations or uses by people.
-
C.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
D.
isHistoricOffice
Indicates that an office or position has historical significance, typically due to its age, legacy, or role in past events.
-
E.
hasPastOccupation
chosen
Indicates that an entity previously held a particular job, role, or occupation in the past.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47acd780c8190b1308ef0aca00f5c |
completed | April 19, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:09 a.m.