Triple
T27888782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMaster |
E705295
|
entity |
| Predicate | electsActiveMasterUsing |
P60317
|
FINISHED |
| Object | ZooKeeper |
—
|
NE NERFINISHED |
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: ZooKeeper | Statement: [HMaster, electsActiveMasterUsing, ZooKeeper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electsActiveMasterUsing Context triple: [HMaster, electsActiveMasterUsing, ZooKeeper]
-
A.
selectionOfLeader
chosen
Indicates the process or act by which one entity is chosen or designated as the leader among a group of entities.
-
B.
electsRole
Indicates that one entity selects or votes another entity into a specific role or position.
-
C.
hasMajorityLeader
Indicates that one entity serves as the primary or leading decision-making authority (majority leader) for another entity, typically within a governing or organizational body.
-
D.
concurrentElection
Indicates that two or more elections are held at the same time or during overlapping time periods.
-
E.
handledElection
Indicates that an entity was responsible for organizing, managing, or overseeing the conduct of an election.
- 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_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: April 27, 2026, 6:34 p.m.