Triple
T27888582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HiveQL |
E705291
|
entity |
| Predicate | supportsComplexType |
P24486
|
FINISHED |
| Object | ARRAY |
—
|
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: ARRAY | Statement: [HiveQL, supportsComplexType, ARRAY]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsComplexType Context triple: [HiveQL, supportsComplexType, ARRAY]
-
A.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
B.
givesComplexStructureCompatibilityTo
Indicates that one entity provides or imparts compatibility for handling or integrating with complex structures to another entity.
-
C.
hasComplex
Indicates that one entity possesses, is associated with, or is part of a larger composite structure or complex formed with another entity.
-
D.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
-
E.
supportsExpressionType
Indicates that one entity is capable of handling, processing, or being compatible with a specified type of expression.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_6a0045a7b4c081908e4dedabda7cf790 |
completed | May 10, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_6a0042b148a48190974b173f352e4b7f |
completed | May 10, 2026, 8:32 a.m. |
Created at: April 27, 2026, 6:34 p.m.