Triple
T25457412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flitch of bacon tradition |
E637948
|
entity |
| Predicate | hasEarliestKnownDate |
P113262
|
FINISHED |
| Object | at least 13th 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: at least 13th century | Statement: [Flitch of bacon tradition, hasEarliestKnownDate, at least 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarliestKnownDate Context triple: [Flitch of bacon tradition, hasEarliestKnownDate, at least 13th century]
-
A.
earliestKnownPeriod
chosen
Indicates the earliest historical or temporal period in which the subject is known or documented to have existed, occurred, or been relevant.
-
B.
hasEarliestMajorCorpus
Indicates that one entity is associated with the earliest significant or primary body of work (major corpus) relative to other comparable entities.
-
C.
earliestFindsDateTo
Indicates the earliest known date at which the finding, discovery, or observation of one entity is recorded as relating to another entity.
-
D.
earliestDocumentsDate
Indicates the earliest date on which the associated documents were created, recorded, or became valid.
-
E.
earliestKnownHolder
Indicates that the subject is the first known entity in time to have possessed, held, or been assigned the object.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f72884408190b586de6cd827e1d4 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:10 p.m.