Triple
T19179077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manifold: Time |
E469521
|
entity |
| Predicate | hasScientificElement |
P83017
|
FINISHED |
| Object | cosmology |
—
|
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: cosmology | Statement: [Manifold: Time, hasScientificElement, cosmology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScientificElement Context triple: [Manifold: Time, hasScientificElement, cosmology]
-
A.
hasScience
chosen
Indicates that an entity possesses, includes, or is associated with a particular scientific discipline, content, or attribute.
-
B.
hasScientificValue
Indicates that something possesses significance, usefulness, or merit within scientific research, understanding, or methodology.
-
C.
hasScienceBody
Indicates that an entity is associated with or possesses a scientific body, such as a scientific organization, committee, or authoritative scientific group.
-
D.
isScientific
Indicates that something pertains to or is based on systematic scientific methods, principles, or knowledge.
-
E.
hasScientificInterestIn
Indicates that one entity holds a scientific curiosity, concern, or research focus directed toward another entity.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f619c60c81909d11489525add829 |
completed | April 20, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.