Triple
T8118149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCP |
E189531
|
entity |
| Predicate | loadedFrom |
P5574
|
FINISHED |
| Object | disk system tracks |
—
|
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: disk system tracks | Statement: [CCP, loadedFrom, disk system tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loadedFrom Context triple: [CCP, loadedFrom, disk system tracks]
-
A.
canBeLoadedAt
Indicates that an entity is capable of being placed onto or into another entity (such as a vehicle, container, or system) at a specific location or point in time.
-
B.
convertedFrom
chosen
Indicates that one entity has been transformed or changed in form, type, or representation from another entity.
-
C.
loadType
Indicates the manner or category of how something is loaded, such as the method, configuration, or type of loading applied in a given context.
-
D.
incorporatedFrom
Indicates that one entity was formed, established, or legally created by deriving or transforming from another pre-existing entity.
-
E.
loadBearingFor
Indicates that one entity structurally supports and carries the weight or load of another entity.
- 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_69ca82baad008190ab2859712b9b1607 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4664fef881908b0dc7b158aca398 |
completed | March 31, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69cb368e7f4c81909aabd7716f0de79d |
completed | March 31, 2026, 2:50 a.m. |
Created at: March 30, 2026, 5:33 p.m.