Triple
T10329822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acid3 |
E242845
|
entity |
| Predicate | testResultDisplay |
P93447
|
FINISHED |
| Object | animated visual rendering |
—
|
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: animated visual rendering | Statement: [Acid3, testResultDisplay, animated visual rendering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testResultDisplay Context triple: [Acid3, testResultDisplay, animated visual rendering]
-
A.
testResult
Indicates that an entity has produced a specific outcome or value when subjected to a particular test or evaluation.
-
B.
TestStatus
Indicates the current outcome or state of a test, such as whether it has passed, failed, is in progress, or has not yet been executed.
-
C.
testStatus
Indicates the current outcome or state of a test, such as whether it has passed, failed, or is still in progress.
-
D.
testDetail
Indicates that there is specific, often granular information or attributes associated with a particular test or testing instance.
-
E.
testSuite
Indicates that one entity is a collection or grouping of tests designed to be executed together, typically to validate behavior or functionality.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7fb77348190ac8ff887f6f03450 |
completed | April 7, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f760e88190abea6dcc4f04f2c1 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d7cada7881908beba55a1dc9ecb9 |
completed | April 7, 2026, 10:09 a.m. |
Created at: April 6, 2026, 11:52 a.m.