Triple
T2866099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hatchards |
E63440
|
entity |
| Predicate | hasLongevity |
P585
|
FINISHED |
| Object | continuous operation since 18th 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: continuous operation since 18th century | Statement: [Hatchards, hasLongevity, continuous operation since 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLongevity Context triple: [Hatchards, hasLongevity, continuous operation since 18th century]
-
A.
hasMeanLifetime
Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
-
B.
lifespan
chosen
Indicates the duration of time between an entity’s birth (or creation) and its death (or end).
-
C.
heldForLife
Indicates that something is possessed, controlled, or held by an entity for the entire duration of that entity’s life, without transfer or expiration before death.
-
D.
durationOfUse
Indicates the length of time for which something is used or remains in use.
-
E.
lifePeriod
Indicates the span of time during which an entity exists, is active, or is valid.
- 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfbb7ed4819096ca65391077e2af |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd123ec48190af50a1859aea50b7 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.