Triple
T26971116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopf fibration |
E679319
|
entity |
| Predicate | hasFiberDescribedAs |
P181403
|
FINISHED |
| Object | orbits of the U(1) action on S^3 |
—
|
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: orbits of the U(1) action on S^3 | Statement: [Hopf fibration, hasFiberDescribedAs, orbits of the U(1) action on S^3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFiberDescribedAs Context triple: [Hopf fibration, hasFiberDescribedAs, orbits of the U(1) action on S^3]
-
A.
hasFiber
Indicates that one entity contains, includes, or is characterized by a certain amount or type of fiber.
-
B.
isFiberFed
Indicates that an entity receives or is supplied with fiber as its input or source.
-
C.
hasDescription
Indicates that an entity is associated with a textual description that explains or characterizes it.
-
D.
hasFiberContent
Indicates that one entity contains a specified amount or level of dietary fiber.
-
E.
hasLineDescribing
Indicates that one entity includes or provides a line of text that describes or characterizes another entity.
- 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_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69f77648979c8190b6cdbb835ab8987c |
completed | May 3, 2026, 4:22 p.m. |
Created at: April 27, 2026, 6:39 a.m.