Triple
T37680963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wounded Dove |
E938228
|
entity |
| Predicate | inceptionTimePeriod |
P302
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [The Wounded Dove, inceptionTimePeriod, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inceptionTimePeriod Context triple: [The Wounded Dove, inceptionTimePeriod, 19th century]
-
A.
inceptionTime
Indicates the specific point in time when an entity, event, or relationship begins or is first established.
-
B.
inceptionWithin
Indicates that one event, process, or entity begins or is initiated entirely within the temporal or spatial bounds of another.
-
C.
inceptionDate
Indicates the date on which an entity, event, or relationship was first created, established, or began to exist.
-
D.
inceptionBefore
Indicates that one entity’s beginning, creation, or initiation occurs earlier in time than that of another entity.
-
E.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs 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_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa19e4a88190b04f26c0d4e708fd |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba887821c8190ae93ef1dd389e9c8 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.