Triple
T4493115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gödel's ontological proof |
E100625
|
entity |
| Predicate | furtherDevelopmentPeriod |
P23760
|
FINISHED |
| Object | 1940s |
—
|
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: 1940s | Statement: [Gödel's ontological proof, furtherDevelopmentPeriod, 1940s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: furtherDevelopmentPeriod Context triple: [Gödel's ontological proof, furtherDevelopmentPeriod, 1940s]
-
A.
fundingPeriod
Indicates the time span or duration for which funding is allocated, active, or valid within a financial or grant-related relationship.
-
B.
developedOverPeriod
chosen
Indicates that something was created, expanded, or progressed continuously throughout a specified span of time.
-
C.
preparationPeriod
Indicates the time span allocated before an event or action during which necessary preparations are made.
-
D.
launchPeriod
Indicates the time span during which a launch or deployment activity occurs or is valid.
-
E.
timePeriodProposed
Indicates that a specific time period has been suggested or put forward for consideration or adoption.
- 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_69bd43cdf15081909a4fa2585ff63b3e |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5570ba0881908f5fb4f8d0730e64 |
completed | March 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69bd5213e3d0819094b026989e686f01 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 12:59 p.m.