Triple
T34244169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wood Quay |
E878550
|
entity |
| Predicate | earliestSignificantOccupationCentury |
P77435
|
FINISHED |
| Object | 9th century |
—
|
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: 9th century | Statement: [Wood Quay, earliestSignificantOccupationCentury, 9th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestSignificantOccupationCentury Context triple: [Wood Quay, earliestSignificantOccupationCentury, 9th century]
-
A.
earliestMajorOccupation
Indicates the earliest significant occupation or professional role held by an entity in its life or career timeline.
-
B.
firstPerformedCentury
Indicates the century in which an action, work, or performance was first carried out or presented.
-
C.
flourishedInCentury
Indicates that an entity experienced its peak activity, influence, or development during a specified century.
-
D.
declaredInCentury
Indicates that something (such as an event, work, or concept) was formally declared or proclaimed during a specified century.
-
E.
earliestOccupationPeriod
chosen
Indicates the time period during which an entity was first occupied or used, before any later occupation periods.
- 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_69f349b3618481909df955b063f305b2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 1, 2026, 1:56 a.m.