Triple
T32541113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Commissioner of Works |
E831713
|
entity |
| Predicate | isHistoricalPosition |
P145233
|
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: [First Commissioner of Works, isHistoricalPosition, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricalPosition Context triple: [First Commissioner of Works, isHistoricalPosition, true]
-
A.
hasHistoricalPosition
chosen
Indicates that an entity has held a specific role, office, or position during a past historical period.
-
B.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
C.
isHistoricFor
Indicates that something has historical significance, relevance, or impact specifically in relation to a given entity or context.
-
D.
historicalPositionStructure
Indicates a relationship where an entity’s role, title, or position is defined within a historically specific organizational or structural context.
-
E.
hasHistoricalData
Indicates that an entity possesses recorded information or records about past events, states, or values relevant to it.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c57f14348190a0e2b98597e5ba25 |
completed | May 3, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:02 a.m.