Triple
T4279777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BI Engine |
E97119
|
entity |
| Predicate | performanceGoal |
P49728
|
FINISHED |
| Object | sub-second to low-second query latency |
—
|
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: sub-second to low-second query latency | Statement: [BI Engine, performanceGoal, sub-second to low-second query latency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceGoal Context triple: [BI Engine, performanceGoal, sub-second to low-second query latency]
-
A.
performanceFocus
Indicates that an entity directs attention or effort toward improving or emphasizing performance in a given context.
-
B.
goals
Indicates that an entity has objectives, targets, or desired outcomes it aims to achieve.
-
C.
performance
Indicates that one entity’s effectiveness, quality, or success in carrying out a task, function, or role is being evaluated or characterized in relation to some standard or expectation.
-
D.
strategicGoal
Indicates that one entity represents a long-term objective or desired outcome that another entity is intentionally aiming to achieve or align actions toward.
-
E.
engineeringGoal
chosen
Indicates that an entity has a specific engineering-related objective, target, or desired outcome it is intended to achieve or support.
- 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_69b34544be3c819084d1ab82d29f90c5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b350367da48190b735deef9b5d2d2e |
completed | March 12, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69b347fc4c0c8190a7fcd814e27308a5 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.