Triple
T35430105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Profsoyuznaya |
E1024031
|
entity |
| Predicate | hasPlatformSurface |
P40183
|
FINISHED |
| Object | granite |
—
|
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: granite | Statement: [Profsoyuznaya, hasPlatformSurface, granite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlatformSurface Context triple: [Profsoyuznaya, hasPlatformSurface, granite]
-
A.
hasSurfaceOperations
Indicates that an entity performs, supports, or is associated with activities or operations occurring on a surface.
-
B.
hasPrimarySurface
chosen
Indicates that one entity serves as the main or principal surface associated with another entity.
-
C.
hasSurfacePreference
Indicates that an entity tends to favor or is best suited for interacting with a particular type of surface over others.
-
D.
hasPlatformType
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
E.
hasTargetPlatform
Indicates that something is intended to run on, be compatible with, or be deployed to a specified platform.
- 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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: May 3, 2026, 4:03 p.m.