Triple
T8492488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foundation universe |
E201005
|
entity |
| Predicate | hasScience |
P83017
|
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: [Foundation universe, hasScience, psychohistory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScience Context triple: [Foundation universe, hasScience, psychohistory]
-
A.
hasScienceBody
Indicates that an entity is associated with or possesses a scientific body, such as a scientific organization, committee, or authoritative scientific group.
-
B.
isScientific
Indicates that something pertains to or is based on systematic scientific methods, principles, or knowledge.
-
C.
hasScientificValue
Indicates that something possesses significance, usefulness, or merit within scientific research, understanding, or methodology.
-
D.
hasScienceCenter
Indicates that an entity possesses, hosts, or includes a science center as one of its facilities or components.
-
E.
hasScientificStudy
Indicates that there exists a scientific study that investigates, analyzes, or provides evidence about the referenced entity or relationship.
- F. None of above. chosen
Provenance (4 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe55cf5dc81908cad31ac53e15b46 |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:13 p.m.