Triple
T36643356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Code Morphing Software |
E904638
|
entity |
| Predicate | loadedAt |
P64343
|
FINISHED |
| Object | system boot |
—
|
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 boot | Statement: [Code Morphing Software, loadedAt, system boot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loadedAt Context triple: [Code Morphing Software, loadedAt, system boot]
-
A.
loadedWith
Indicates that one entity is carrying, filled with, or heavily supplied with another entity.
-
B.
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.
-
C.
isUnloadedAt
Indicates that an object or cargo is removed from a vehicle, container, or transport and placed at a specific location.
-
D.
loader
Indicates a relationship where an entity is responsible for loading or placing items, data, or resources into another system, container, or context.
-
E.
compiledAt
chosen
Indicates that one entity was built or transformed into an executable or final form at a specific time or location represented by the other 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_69f76e6d3a3c81909db73eda9e0516bd |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.