Triple
T24791714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GT Daytona |
E620267
|
entity |
| Predicate | balanceOfPerformance |
P157135
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [GT Daytona, balanceOfPerformance, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: balanceOfPerformance Context triple: [GT Daytona, balanceOfPerformance, yes]
-
A.
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.
-
B.
basedOnPerformanceBy
Indicates that something is derived from, adapted from, or determined according to the performance carried out by a particular entity.
-
C.
performanceWith
Indicates a relationship where two or more entities participate together in the same performance or staged presentation.
-
D.
performanceBasis
Indicates that one entity’s performance is evaluated, determined, or justified on the basis of another specified factor, standard, or reference.
-
E.
positionInPerformance
Indicates the specific ordering or placement of an entity within a performance or sequence of performed elements.
- F. None of above. chosen
Provenance (4 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f4110424188190889a13976b16b18a |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f410a001788190a457e41f53aaf90c |
completed | May 1, 2026, 2:32 a.m. |
Created at: April 18, 2026, 4:47 a.m.