Triple
T3044195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tucker’s lemma |
E83404
|
entity |
| Predicate | hasInput |
P44777
|
FINISHED |
| Object | antipodally symmetric triangulation of a sphere |
—
|
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: antipodally symmetric triangulation of a sphere | Statement: [Tucker’s lemma, hasInput, antipodally symmetric triangulation of a sphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInput Context triple: [Tucker’s lemma, hasInput, antipodally symmetric triangulation of a sphere]
-
A.
hasInputType
Indicates that an entity takes another entity as its input type for its operation, function, or process.
-
B.
hasInlet
Indicates that one entity serves as an inlet or entry point through which another entity receives a flow of material, energy, or fluid.
-
C.
hasKeyboard
Indicates that one entity possesses or is equipped with a keyboard as a component or accessory.
-
D.
hasInteraction
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
E.
hasCurrent
Indicates that an entity presently possesses, exhibits, or is associated with a particular state, attribute, or resource at the current time.
- 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9b5ec5988190b8b6c95c743c6d1e |
completed | March 8, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69ad961fc62c819087c4c3a44b00847d |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f6af3881909f4547967384114c |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3:01 p.m.