Triple
T19940279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon Marius |
E479289
|
entity |
| Predicate | supportedModel |
P137919
|
FINISHED |
| Object | geocentric cosmology |
—
|
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: geocentric cosmology | Statement: [Simon Marius, supportedModel, geocentric cosmology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedModel Context triple: [Simon Marius, supportedModel, geocentric cosmology]
-
A.
supportsModelType
Indicates that an entity is compatible with, or can operate using, a specified model type.
-
B.
supportsModelFamily
Indicates that one entity provides compatibility, functionality, or resources necessary for the operation or use of a particular model family.
-
C.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
D.
supportedMode
Indicates that a system, device, or component is capable of operating in or handling a particular mode.
-
E.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a1a8df4819094e84855465df6c0 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:53 p.m.