Triple
T4443225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LinearAlgebra |
E96219
|
entity |
| Predicate | exportsFunction |
P38257
|
FINISHED |
| Object | dot |
—
|
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: dot | Statement: [LinearAlgebra, exportsFunction, dot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exportsFunction Context triple: [LinearAlgebra, exportsFunction, dot]
-
A.
publicFunction
Indicates that a function or method is accessible from outside its defining scope, module, or class (i.e., it has public visibility).
-
B.
exercisesFunction
Indicates that one entity performs or carries out the function, role, or capability associated with another entity.
-
C.
usesFunction
chosen
Indicates that one entity employs, invokes, or relies on a particular function to perform an operation or achieve a result.
-
D.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
-
E.
functionInWork
Indicates that a particular function, role, or operation is performed, utilized, or occurs within the context of a specific work or creation.
- 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.