Triple
T4566391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tychonic system |
E121919
|
entity |
| Predicate | developedAroundYear |
P95
|
FINISHED |
| Object | late 1500s |
—
|
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: late 1500s | Statement: [Tychonic system, developedAroundYear, late 1500s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedAroundYear Context triple: [Tychonic system, developedAroundYear, late 1500s]
-
A.
developedAround
Indicates that one entity was created, designed, or evolved with the other entity as its central focus, basis, or surrounding context.
-
B.
developedAt
Indicates the place or location where something was created, built, or developed.
-
C.
developedSince
Indicates that something has been created, expanded, or advanced starting from a specified point in time and continuing thereafter.
-
D.
wasDevelopedInPeriod
chosen
Indicates that something was created, produced, or brought into existence during a specified time period.
-
E.
discoveryYear
Indicates the calendar year in which something was first discovered or identified.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd589e35808190aa609bb04b128dbe |
completed | March 20, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.