Triple
T4443246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LinearAlgebra |
E96219
|
entity |
| Predicate | isLoadedWith |
P2301
|
FINISHED |
| Object | using LinearAlgebra |
—
|
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: using LinearAlgebra | Statement: [LinearAlgebra, isLoadedWith, using LinearAlgebra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLoadedWith Context triple: [LinearAlgebra, isLoadedWith, using LinearAlgebra]
-
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.
launchedWith
Indicates that one entity was initiated, started, or set into motion together with another entity as part of the same launch event.
-
C.
isGivenBy
Indicates that something (such as an item, value, or information) is provided or granted by a particular source or giver.
-
D.
executedWith
chosen
Indicates that an action or process was carried out using, accompanied by, or in conjunction with a specified tool, method, or participant.
-
E.
compliedWith
Indicates that one entity has acted in accordance with, or fulfilled the requirements of, another entity’s rules, requests, or standards.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355aef21c819088f168a23f1933a6 |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.