Triple
T18256066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GHC |
E437224
|
entity |
| Predicate | providesTool |
P28572
|
FINISHED |
| Object | ghc compiler executable |
—
|
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: ghc compiler executable | Statement: [GHC, providesTool, ghc compiler executable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesTool Context triple: [GHC, providesTool, ghc compiler executable]
-
A.
officialToolFor
Indicates that one entity is formally designated or authorized as the standard or primary tool to be used for another entity or purpose.
-
B.
toolIn
chosen
Indicates that one entity is a tool or instrument used in or associated with another entity or context.
-
C.
usesToolFor
Indicates that an agent employs a specific tool to carry out or facilitate a particular action or purpose.
-
D.
toolDeveloperFor
Indicates that one entity is the creator or developer of a tool that is used by or associated with another entity.
-
E.
relatedTool
Indicates that one tool has a meaningful association or connection with another tool, such as being complementary, compatible, or commonly used together.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4fd85ee548190a102611fcf709ad4 |
completed | April 19, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.