Triple
T34545759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitehead product |
E886920
|
entity |
| Predicate | outputCondition |
P29885
|
FINISHED |
| Object | [α,β] ∈ π_{m+n-1}(X) |
—
|
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: [α,β] ∈ π_{m+n-1}(X) | Statement: [Whitehead product, outputCondition, [α,β] ∈ π_{m+n-1}(X)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outputCondition
Context triple: [Whitehead product, outputCondition, [α,β] ∈ π_{m+n-1}(X)]
-
A.
returnCondition
Indicates the terms, state, or circumstances under which something that was previously given, lent, or transferred is expected or required to be returned.
-
B.
canCondition
Indicates that one entity has the capability or potential to impose, apply, or bring about a particular condition on another entity or situation.
-
C.
captureCondition
Indicates the specific circumstances or criteria under which a capture event or action is triggered or considered valid.
-
D.
triggerCondition
chosen
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
-
E.
modificationCondition
Indicates the specific circumstances or requirements under which a change or modification to something is permitted, triggered, or becomes applicable.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7201fc32c8190a79a85a7a4f63662 |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.