Triple
T35208872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DOMQuad |
E1016614
|
entity |
| Predicate | supportsHitTestingUseCases |
P15794
|
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: [DOMQuad, supportsHitTestingUseCases, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHitTestingUseCases Context triple: [DOMQuad, supportsHitTestingUseCases, true]
-
A.
supportsTestType
Indicates that one entity is capable of handling, executing, or being compatible with a specified type of test.
-
B.
hasUseCase
Indicates that one entity is employed, applied, or utilized as a solution or method to address a particular need, problem, or scenario associated with another entity.
-
C.
supportsUserInteraction
Indicates that an entity enables or facilitates direct interaction with a user, such as receiving input or providing responsive feedback.
-
D.
testedUnder
Indicates that one entity is examined, evaluated, or experimented on while being subject to the conditions, environment, or parameters specified by another entity.
-
E.
supportsUse
chosen
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.