Triple
T6361365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firwood Fold |
E143115
|
entity |
| Predicate | hasApproximateOriginCentury |
P14813
|
FINISHED |
| Object | 17th 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: 17th century | Statement: [Firwood Fold, hasApproximateOriginCentury, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateOriginCentury Context triple: [Firwood Fold, hasApproximateOriginCentury, 17th century]
-
A.
approximateStartCentury
chosen
Indicates the century in which something is estimated or roughly believed to have begun.
-
B.
approximateStartCenturyBC
Indicates that an entity’s starting time or occurrence is approximately located within a specified century before the Common Era (BC).
-
C.
originalCentury
Indicates the century in which something was originally created, produced, or came into existence.
-
D.
attestedFromCentury
Indicates the century from which there is evidence or documentation that something is known to exist or be in use.
-
E.
attestedUntilCentury
Indicates the latest century up to which the existence or use of something is historically documented or evidenced.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067fa0d0c819098d01545849142fc |
completed | March 22, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69c060ec091c8190912aac44e1b8b1c9 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:32 p.m.