Triple
T16128812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Wiltshire |
E391339
|
entity |
| Predicate | hasRecreatedRepresentationStart |
P30447
|
FINISHED |
| Object | 1983 |
—
|
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: 1983 | Statement: [North Wiltshire, hasRecreatedRepresentationStart, 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecreatedRepresentationStart Context triple: [North Wiltshire, hasRecreatedRepresentationStart, 1983]
-
A.
hasFirstCreation
Indicates that one entity is the earliest or initial creation produced by another entity.
-
B.
hasRebuilt
Indicates that an entity has restored, reconstructed, or built again something that previously existed or was damaged or destroyed.
-
C.
hasMultipleCreations
Indicates that an entity is associated with more than one distinct creation or produced work.
-
D.
hasRepresentationFrom
Indicates that something serves as a representation, depiction, or encoding that originates from or is derived from another entity.
-
E.
regenerationStartedIn
chosen
Indicates that a regeneration process was initiated or began within a specified location, context, or time frame.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e20206a6f08190aa648d2bb11e7878 |
completed | April 17, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.