Triple
T6801428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poincaré duality |
E156194
|
entity |
| Predicate | failsWithout |
P8788
|
FINISHED |
| Object | orientability |
—
|
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: orientability | Statement: [Poincaré duality, failsWithout, orientability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: failsWithout Context triple: [Poincaré duality, failsWithout, orientability]
-
A.
failsWhen
chosen
Indicates that a particular action, process, or condition does not succeed under the specified circumstances or triggers.
-
B.
failedOn
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
-
C.
succeedsInAbsenceOf
Indicates that one entity successfully achieves or maintains something only when another specified entity or condition is not present.
-
D.
missionFailure
Indicates that an attempted mission or operation did not achieve its intended objectives or outcome.
-
E.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
- 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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2e595188190a0bb4b595df3adb2 |
completed | March 27, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:16 p.m.