Triple
T26971087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopf fibration |
E679319
|
entity |
| Predicate | wasIntroducedInField |
P164304
|
FINISHED |
| Object | algebraic topology |
—
|
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: algebraic topology | Statement: [Hopf fibration, wasIntroducedInField, algebraic topology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasIntroducedInField Context triple: [Hopf fibration, wasIntroducedInField, algebraic topology]
-
A.
fieldIntroduced
Indicates that a particular field or attribute was newly added or introduced into a data structure, schema, or record.
-
B.
introducedFrom
Indicates that one entity was brought, originated, or caused to appear in a context, system, or environment by another entity.
-
C.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
D.
settingIntroducedIn
Indicates the work, installment, or context in which a particular setting first appears or is established.
-
E.
areIntroducedBy
Indicates that one entity becomes known or presented to another entity through the action or mediation of a third party or process.
- 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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 6:39 a.m.