Triple
T29613890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galactic Foundation |
E754806
|
entity |
| Predicate | basedOnScience |
P26758
|
FINISHED |
| Object | psychohistory |
—
|
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: psychohistory | Statement: [Galactic Foundation, basedOnScience, psychohistory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnScience Context triple: [Galactic Foundation, basedOnScience, psychohistory]
-
A.
hasScientificBasis
Indicates that something is supported, justified, or grounded by established scientific evidence, methods, or principles.
-
B.
hasScience
Indicates that an entity possesses, includes, or is associated with a particular scientific discipline, content, or attribute.
-
C.
consideredByScience
Indicates that something is regarded, evaluated, or treated as valid or relevant within the framework, methods, or consensus of scientific inquiry.
-
D.
isScientific
chosen
Indicates that something pertains to or is based on systematic scientific methods, principles, or knowledge.
-
E.
basedOnFactFrom
Indicates that something is derived, justified, or constructed using factual information obtained from a specified source.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: April 28, 2026, 6:30 p.m.