Triple
T1056904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brouwer fixed-point theorem |
E22815
|
entity |
| Predicate | domainCondition |
P19924
|
FINISHED |
| Object | compact set |
—
|
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: compact set | Statement: [Brouwer fixed-point theorem, domainCondition, compact set]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domainCondition Context triple: [Brouwer fixed-point theorem, domainCondition, compact set]
-
A.
authorizationCondition
Indicates the specific rules or requirements that must be satisfied for an action or access to be legally or formally authorized.
-
B.
coreCondition
chosen
Indicates that something serves as the primary or fundamental condition that must hold for a situation, process, or relationship to apply.
-
C.
localityCondition
Indicates a spatial or contextual constraint specifying where or under what local conditions a relationship, event, or property holds.
-
D.
navigationCondition
Indicates the specific circumstances or requirements that must be satisfied for a navigation action or route to be valid or taken.
-
E.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8da80dc8190b79beaf509910725 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b731e25c8190b5ea8466648c2c9a |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.