Triple
T34368306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Foundling |
E882080
|
entity |
| Predicate | associatedWithSettingCentury |
P56280
|
FINISHED |
| Object | 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: 18th century | Statement: [A Foundling, associatedWithSettingCentury, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSettingCentury Context triple: [A Foundling, associatedWithSettingCentury, 18th century]
-
A.
associatedWithCentury
chosen
Indicates that something has a relevant connection or linkage to a particular century, such as occurring in, belonging to, or being characteristic of that time period.
-
B.
associatedWithCenturyOfNameBearer
Indicates that an entity is linked to the historical century in which the person (name bearer) associated with it lived or is primarily known.
-
C.
ownedInCentury
Indicates that one entity owned another during a specified century.
-
D.
usedInCentury
Indicates that something (such as an object, practice, or concept) was in use during a specified century.
-
E.
originalCentury
Indicates the century in which something was originally created, produced, or came into existence.
- 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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:58 a.m.