Triple
T32299924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hampstead and Highgate |
E825207
|
entity |
| Predicate | lastUsedIn |
P173941
|
FINISHED |
| Object | 2005–2010 Parliament |
—
|
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: 2005–2010 Parliament | Statement: [Hampstead and Highgate, lastUsedIn, 2005–2010 Parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastUsedIn Context triple: [Hampstead and Highgate, lastUsedIn, 2005–2010 Parliament]
-
A.
lastUsedFor
Indicates that one entity was the most recent purpose, function, or application for which another entity was used.
-
B.
lastYearOfUse
Indicates the final year in which something was actively used or in operation.
-
C.
inUseSince
Indicates that an entity has been actively in use starting from a specified point in time.
-
D.
lastSeenOn
Indicates the most recent time or date at which the subject entity was observed, detected, or recorded.
-
E.
usedSince
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
- 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bd70b43c819086d1e5f1df5aec86 |
completed | May 3, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:45 a.m.