Triple
T7985652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apache Hive |
E185675
|
entity |
| Predicate | runsOn |
P23
|
FINISHED |
| Object | Hadoop YARN |
E185672
|
NE 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: Hadoop YARN | Statement: [Apache Hive, runsOn, Hadoop YARN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hadoop YARN Context triple: [Apache Hive, runsOn, Hadoop YARN]
-
A.
YARN
chosen
YARN (Yet Another Resource Negotiator) is Hadoop’s cluster resource management and job scheduling framework that coordinates and allocates system resources for distributed data processing applications.
-
B.
Hadoop
Hadoop is an open-source framework that enables distributed storage and parallel processing of large data sets across clusters of commodity hardware.
-
C.
Apache Tez
Apache Tez is a distributed data processing framework designed for building high-performance batch and interactive data workflows on Hadoop.
-
D.
yarn
Yarn is a fast, reliable JavaScript package manager that serves as an alternative to npm for managing project dependencies.
-
E.
HDFS
HDFS (Hadoop Distributed File System) is a fault-tolerant, distributed file system designed to store and manage large volumes of data across clusters of commodity hardware.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca829a2cfc819083d591d58ec04075 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c4a55b881909a96133e56c0dffa |
completed | March 31, 2026, 3:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc567cfe548190bbd163a32c340bcc |
completed | March 31, 2026, 11:19 p.m. |
Created at: March 30, 2026, 5:15 p.m.