Triple
T4443202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LinearAlgebra |
E96219
|
entity |
| Predicate | providesFunctionalityFor |
P40816
|
FINISHED |
| Object | vectors |
—
|
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: vectors | Statement: [LinearAlgebra, providesFunctionalityFor, vectors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesFunctionalityFor Context triple: [LinearAlgebra, providesFunctionalityFor, vectors]
-
A.
providesFunctionalityOf
chosen
Indicates that one entity supplies, implements, or makes available the capabilities or functions that are normally associated with another entity.
-
B.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
-
C.
definesFunctioningOf
Indicates that one entity specifies or determines how another entity operates or functions.
-
D.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
-
E.
providesThat
Indicates that one entity stipulates, specifies, or sets forth a condition, rule, or provision that applies to another entity or situation.
- 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.