Triple
T14343449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SBT |
E355656
|
entity |
| Predicate | supportsBuildDefinition |
P83855
|
FINISHED |
| Object | build.sbt file |
—
|
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: build.sbt file | Statement: [SBT, supportsBuildDefinition, build.sbt file]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBuildDefinition Context triple: [SBT, supportsBuildDefinition, build.sbt file]
-
A.
supportsCodeBuilder
Indicates that an entity provides compatibility with or functionality for a code-building tool or environment.
-
B.
supportsBuildManifestFormat
chosen
Indicates that one entity is capable of handling or is compatible with a specified build manifest format used in a build process.
-
C.
supportsProjectType
Indicates that one entity is capable of handling, accommodating, or being compatible with a specified type of project.
-
D.
supportsStyleDefinition
Indicates that one entity is capable of handling, recognizing, or working with a particular style definition associated with another entity.
-
E.
hasBuildTool
Indicates that an entity uses or is associated with a specific tool or system for building, compiling, or assembling software or other artifacts.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e89ed9c8190acdb647ee618e919 |
completed | April 14, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:14 a.m.