Triple
T1390479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surreal numbers |
E29943
|
entity |
| Predicate | containsAsSubfield |
P28231
|
FINISHED |
| Object | real numbers |
—
|
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 | Statement: [Surreal numbers, containsAsSubfield, real numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsAsSubfield Context triple: [Surreal numbers, containsAsSubfield, real numbers]
-
A.
containsAsSubstructure
Indicates that one structure includes another structure entirely within it as a component or embedded part.
-
B.
hasSubConcept
Indicates that one concept is a more specific, subordinate, or narrower idea within the scope of another, more general concept.
-
C.
hasSubfieldGroup
Indicates that an entity includes or is associated with a specific subgroup of related subfields within its overall structure or domain.
-
D.
containsSubchapter
Indicates that one chapter or section includes another, more specific subchapter as a part of its structure.
-
E.
belongsToSubfamily
Indicates that one entity is a member of, or classified within, a specific subfamily of another entity.
- F. None of above. chosen
Provenance (4 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c35e023c8190b45688796d90534b |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c2f16ae081908c92792253f3eb4b |
completed | March 1, 2026, 10:51 p.m. |
Created at: March 1, 2026, 7:59 p.m.