Triple
T16900338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crawley Borough Council |
E424417
|
entity |
| Predicate | lastMajorBoundaryChangesYear |
P46007
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [Crawley Borough Council, lastMajorBoundaryChangesYear, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastMajorBoundaryChangesYear Context triple: [Crawley Borough Council, lastMajorBoundaryChangesYear, 2004]
-
A.
previousMajorRevisionYear
Indicates the calendar year in which the immediately preceding major revision or version of an item was released or finalized.
-
B.
majorRevisionYear
Indicates the year in which a significant or primary revision of something (such as a work, document, or standard) was made.
-
C.
lastDelimitationYear
chosen
Indicates the year in which the most recent boundary or delimitation of the entity was officially established or updated.
-
D.
yearOfMajorMigration
Indicates the specific year in which a significant migration event involving the subject took place.
-
E.
finalVersionYear
Indicates the year in which the final or last version of something was completed, released, or became definitive.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8dbc6e48190be90066b82fc61db |
completed | April 18, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.