Triple
T11735371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chatham Dockyard |
E279011
|
entity |
| Predicate | employedAtPeak |
P23435
|
FINISHED |
| Object | over 10,000 workers |
—
|
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: over 10,000 workers | Statement: [Chatham Dockyard, employedAtPeak, over 10,000 workers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employedAtPeak Context triple: [Chatham Dockyard, employedAtPeak, over 10,000 workers]
-
A.
workAt
Indicates that an entity is employed by or performs work for a particular organization, company, or place.
-
B.
employedTo
Indicates that one entity is hired or engaged to perform work, services, or duties for another entity.
-
C.
peakEmployment
chosen
Indicates that an entity has reached its highest level of employment or workforce size during a specified period.
-
D.
workedAs
Indicates that an entity held a particular job, role, or position, performing work in that capacity.
-
E.
employerIn
Indicates that one entity serves as the employer of another within a specified context, such as a location, organization, or time period.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4edced48190b7a59dd45921828e |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.