Triple
T24438058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia Galilei |
E616177
|
entity |
| Predicate | correspondenceTimeSpan |
P9341
|
FINISHED |
| Object | early 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: early 17th century | Statement: [Virginia Galilei, correspondenceTimeSpan, early 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondenceTimeSpan Context triple: [Virginia Galilei, correspondenceTimeSpan, early 17th century]
-
A.
followsTimeSpan
Indicates that one time span occurs immediately or subsequently after another specified time span.
-
B.
timeSpanMentioned
Indicates that a specific duration or period of time is explicitly referenced in the context.
-
C.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
D.
collectionTimespan
chosen
Indicates the time period over which a collection exists, is accumulated, or is considered valid.
-
E.
documentationPeriod
Indicates the time span or interval during which something is documented, recorded, or valid in the documentation.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f297881fa08190b82bdc5ebeae96f7 |
completed | April 29, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:16 a.m.