Triple
T16112810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Suitor’s Visit |
E390920
|
entity |
| Predicate | creatorActivePeriod |
P90217
|
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: [The Suitor’s Visit, creatorActivePeriod, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creatorActivePeriod Context triple: [The Suitor’s Visit, creatorActivePeriod, 17th century]
-
A.
creatorLifespan
Indicates the time period between the birth and death of the creator associated with an entity.
-
B.
hasCreativePeriod
chosen
Indicates that an entity is associated with a specific span of time during which it produced or engaged in notable creative work.
-
C.
activeFrom
Indicates the starting point in time from which an entity or relationship is considered active or in effect.
-
D.
activeAt
Indicates that an entity is functioning, valid, or in effect during a specified time or at a particular location or context.
-
E.
registrationPeriod
Indicates the time span during which registration for something is open or 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e20168bf98819093c3260d4fde2b53 |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.