Triple
T31238604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High-feature V6 |
E796494
|
entity |
| Predicate | intendedBalance |
P9277
|
FINISHED |
| Object | performance |
—
|
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: performance | Statement: [High-feature V6, intendedBalance, performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedBalance Context triple: [High-feature V6, intendedBalance, performance]
-
A.
aimsToBalance
chosen
Indicates an intention or effort by one entity to bring multiple elements, forces, or conditions into a state of equilibrium.
-
B.
balanceType
Indicates the category or nature of a balance associated with an entity, such as how that balance is classified or treated.
-
C.
balanceControl
Indicates the extent to which one entity regulates, maintains, or stabilizes the equilibrium or proportional distribution of another entity or system.
-
D.
balancesWith
Indicates that two entities are in a state of equilibrium or mutual offset, such that each counterbalances or matches the other in a specified context.
-
E.
hasMaximumBalanceLimit
Indicates that there is an upper bound on the balance that an account or entity is allowed to hold.
- 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_69f224db69ac81909a370adad6a7ac7c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 29, 2026, 9:11 p.m.