Triple
T34471567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montel space |
E884920
|
entity |
| Predicate | oftenAssumedToBe |
P50642
|
FINISHED |
| Object | Hausdorff |
—
|
NE NERFINISHED |
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: Hausdorff | Statement: [Montel space, oftenAssumedToBe, Hausdorff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenAssumedToBe Context triple: [Montel space, oftenAssumedToBe, Hausdorff]
-
A.
typicalAssumption
Indicates that something is taken as a standard or default assumption that generally holds in typical or normal circumstances.
-
B.
oftenHeldToBe
Indicates that something is frequently regarded, considered, or believed to be a certain way by many people or in many contexts.
-
C.
assumes
Indicates that one entity takes on, accepts, or presumes a role, responsibility, state, or fact regarding another entity or situation.
-
D.
oftenStatedWith
Indicates that one statement, fact, or expression is frequently mentioned or asserted together with another.
-
E.
isAssumedIn
chosen
Indicates that something is taken for granted or presumed to hold within a particular context, without requiring explicit proof or verification.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: May 1, 2026, 2:01 a.m.