Triple
T6751229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Life of Galileo |
E154343
|
entity |
| Predicate | firstVersionCompletedIn |
P51515
|
FINISHED |
| Object | 1939 |
—
|
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: 1939 | Statement: [Life of Galileo, firstVersionCompletedIn, 1939]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstVersionCompletedIn Context triple: [Life of Galileo, firstVersionCompletedIn, 1939]
-
A.
firstVersionYear
chosen
Indicates the calendar year in which the first version or initial release of something was created, published, or made available.
-
B.
firstReleaseVersion
Indicates the specific version identifier associated with the initial public release of something.
-
C.
firstRelease
Indicates that one entity is the initial or earliest release (in time or sequence) of another entity, such as a product, work, or version.
-
D.
firstCompleterYear
Indicates the calendar or academic year in which an entity first completed a specified program, requirement, or activity.
-
E.
firstFullVersionReference
Indicates that one entity serves as the initial complete or fully realized version to which another entity refers or is linked.
- 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_69c6880ef37881909268a5a7299b9293 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d327e37081909d576e6eff9eec97 |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09227108190b253b91967831a85 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:11 p.m.