Triple
T27133613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baire space |
E681622
|
entity |
| Predicate | isUsedToCode |
P3746
|
FINISHED |
| Object | real numbers in descriptive set theory |
—
|
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: real numbers in descriptive set theory | Statement: [Baire space, isUsedToCode, real numbers in descriptive set theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedToCode Context triple: [Baire space, isUsedToCode, real numbers in descriptive set theory]
-
A.
isUsedToTest
Indicates that one entity serves as a means or tool for evaluating, examining, or verifying another entity.
-
B.
isBelievedToBeUsedFor
Indicates that something is thought or assumed to serve a particular purpose or function, without certainty.
-
C.
isSometimesUsedFor
Indicates that something serves a particular purpose or function on some occasions, but not consistently or exclusively.
-
D.
codeFor
chosen
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
E.
isOfficialCodeFor
Indicates that one entity serves as the formally recognized or authorized code that designates or identifies another entity.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 9:05 a.m.