Triple
T33960880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hartlib Circle |
E870711
|
entity |
| Predicate | hasActivityPeriodEnd |
P118268
|
FINISHED |
| Object | 1660s |
—
|
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: 1660s | Statement: [Hartlib Circle, hasActivityPeriodEnd, 1660s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasActivityPeriodEnd Context triple: [Hartlib Circle, hasActivityPeriodEnd, 1660s]
-
A.
hasRecentActivity
Indicates that the subject has performed an action or been involved in an event within a defined recent time period.
-
B.
activePeriodApproximate
Indicates that the time span during which an entity was active is known only approximately rather than as precise dates.
-
C.
hasCollectionEndDate
Indicates the date on which a collection activity, period, or process is scheduled or recorded to end.
-
D.
hasActivityStatus
Indicates the current state or condition of an activity, such as whether it is planned, ongoing, completed, or cancelled.
-
E.
hasTemporalEnd
chosen
Indicates that an event, state, or process concludes or terminates at a specific point or interval in time.
- 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_69f3499ce8e88190b66e1d49ad8c7037 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 1, 2026, 1:50 a.m.