Triple
T5916035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etruria, Staffordshire |
E131581
|
entity |
| Predicate | openedForIndustry |
P67677
|
FINISHED |
| Object | late 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: late 18th century | Statement: [Etruria, Staffordshire, openedForIndustry, late 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForIndustry Context triple: [Etruria, Staffordshire, openedForIndustry, late 18th century]
-
A.
openedForUse
Indicates that something has been made accessible and available for its intended operation or use.
-
B.
openedForPublic
Indicates that something has been made accessible or available for use, entry, or participation by the general public.
-
C.
openedForThroughService
Indicates that an entity has been made accessible or available specifically for use via a through-service connection or route, rather than as a standalone endpoint.
-
D.
openedForCurrentUse
Indicates that an entity has been opened and is currently available for its intended use or operation.
-
E.
opens
Indicates that one entity causes or allows another entity (such as an object, space, or resource) to become accessible or no longer closed.
- F. None of above. chosen
Provenance (4 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_69c0085a1ed08190a7e9a8b6323fd680 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c048fc112c8190b905bf561c9de096 |
completed | March 22, 2026, 7:54 p.m. |
| PD | Predicate disambiguation | batch_69c03352208c8190968efed05a9fd416 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c048fb02a081908e78629e1e283cd0 |
completed | March 22, 2026, 7:54 p.m. |
Created at: March 22, 2026, 3:59 p.m.