Triple
T1937929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCL |
E41485
|
entity |
| Predicate | fileTypeSSDMeaning |
P13218
|
FINISHED |
| Object | System Specification Description |
—
|
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: System Specification Description | Statement: [SCL, fileTypeSSDMeaning, System Specification Description]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fileTypeSSDMeaning Context triple: [SCL, fileTypeSSDMeaning, System Specification Description]
-
A.
mediaType
Indicates the format or category of media associated with an entity, such as text, image, audio, or video.
-
B.
physicalMediumDependentSubtype
Indicates that one subtype or variation of something is specifically determined or constrained by the physical medium through which it exists or operates.
-
C.
semanticType
Indicates that something belongs to or is categorized under a particular semantic class or type based on its meaning.
-
D.
typicalPictureFormat
chosen
Indicates the standard or most commonly used picture format associated with an entity (such as a device, medium, or context).
-
E.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb2c752fc81909baf38ff1cdeb18c |
completed | March 7, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69abaff07cf88190b4883c5f17f90abd |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.