Triple
T20009946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hartlepool Dock |
E494562
|
entity |
| Predicate | hasDevelopmentPhase |
P114525
|
FINISHED |
| Object | 19th-century expansion |
—
|
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: 19th-century expansion | Statement: [Hartlepool Dock, hasDevelopmentPhase, 19th-century expansion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDevelopmentPhase Context triple: [Hartlepool Dock, hasDevelopmentPhase, 19th-century expansion]
-
A.
hasDevelopmentStatus
Indicates the current stage or condition of progress or completion that something is in.
-
B.
hasDevelopmentType
Indicates the type or category of development associated with an entity, such as the nature, form, or stage of its development.
-
C.
developmentPhaseName
chosen
Indicates the specific stage or phase name within a broader development process or lifecycle.
-
D.
mainDevelopmentPeriod
Indicates the primary time span during which the main development or formation of something took place.
-
E.
hasDevelopmentSystem
Indicates that one entity possesses, uses, or is associated with a particular system, platform, or environment used for development activities.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a81c5881909692fcaaf59a57c9 |
completed | April 20, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:33 p.m.