Triple
T36013357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | homotopy type theory |
E1041770
|
entity |
| Predicate | hasModelIn |
P199402
|
FINISHED |
| Object | simplicial sets |
—
|
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: simplicial sets | Statement: [homotopy type theory, hasModelIn, simplicial sets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModelIn Context triple: [homotopy type theory, hasModelIn, simplicial sets]
-
A.
hasModels
Indicates that an entity possesses, defines, or is associated with one or more models (such as conceptual, mathematical, or data models).
-
B.
hasLocalModel
Indicates that one entity possesses or uses a model that is stored or executed locally rather than accessed remotely.
-
C.
hasModelStatus
Indicates that an entity is assigned a particular model-related state or condition, such as its current phase, validity, or operational status within a modeling context.
-
D.
hasModelType
Indicates that an entity is associated with or classified under a specific model type.
-
E.
hasAccessModel
Indicates that one entity is permitted to use, interact with, or retrieve a particular model controlled by another entity or system.
- 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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69ff3705e424819090ad7423ceefa506 |
completed | May 9, 2026, 1:30 p.m. |
Created at: May 3, 2026, 4:07 p.m.