Triple
T24791761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daytona Prototype international |
E620268
|
entity |
| Predicate | balanceOfPerformanceUsed |
P33238
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Daytona Prototype international, balanceOfPerformanceUsed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: balanceOfPerformanceUsed Context triple: [Daytona Prototype international, balanceOfPerformanceUsed, true]
-
A.
balanceOfPerformance
Indicates a relationship where performance characteristics between entities are adjusted or equalized to maintain fairness or parity.
-
B.
scoreUsedFor
chosen
Indicates that a particular score or rating is used for a specific purpose, decision, or downstream process.
-
C.
totalPerformances
Indicates the total number of times a particular performance, show, or act has been carried out.
-
D.
basedOnPerformanceBy
Indicates that something is derived from, adapted from, or determined according to the performance carried out by a particular entity.
-
E.
hasNumberOfUses
Indicates the quantity of times something can be or is intended to be used.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:47 a.m.