Triple
T3269505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huntingdon (UK Parliament constituency) |
E68608
|
entity |
| Predicate | previouslyExisted |
P35873
|
FINISHED |
| Object | pre-1918 |
—
|
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: pre-1918 | Statement: [Huntingdon (UK Parliament constituency), previouslyExisted, pre-1918]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyExisted Context triple: [Huntingdon (UK Parliament constituency), previouslyExisted, pre-1918]
-
A.
existedAs
chosen
Indicates that one entity had the status, form, or identity of another entity during a certain time or context.
-
B.
previouslyObserved
Indicates that the subject entity has been seen, recorded, or encountered at some earlier time prior to the current context.
-
C.
existedUnder
Indicates that one entity existed within the authority, jurisdiction, or domain of another entity during a certain period.
-
D.
previouslyOutside
Indicates that an entity was located outside a specified area or boundary at some earlier time prior to the current reference point.
-
E.
previouslyDefinedIn
Indicates that something has been defined or introduced earlier in time or in a prior context relative to the current reference point.
- 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adafd0eddc8190834a64f6b8e8e9f9 |
completed | March 8, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69ada41d7eac8190ada4bf5f793d5c49 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.