Triple
T34956727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luminus |
E1008138
|
entity |
| Predicate | primaryBuildTool |
P19952
|
FINISHED |
| Object | Leiningen |
E1008134
|
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: Leiningen | Statement: [Luminus, primaryBuildTool, Leiningen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBuildTool Context triple: [Luminus, primaryBuildTool, Leiningen]
-
A.
hasBuildTool
chosen
Indicates that an entity uses or is associated with a specific tool or system for building, compiling, or assembling software or other artifacts.
-
B.
defaultToolchain
Indicates that a particular toolchain is the primary or automatically selected set of tools used by default for building or processing tasks.
-
C.
includesTooling
Indicates that one entity contains, provides, or comes bundled with specific tools or tooling capabilities related to another entity.
-
D.
toolchain
Indicates a relationship where one entity is used as a coordinated set of tools or processes to build, compile, or transform another entity (typically software or code).
-
E.
isBuilding
Indicates that an entity functions as or is classified as a building.
- F. None of above.
Provenance (4 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37bd0a224c81909ef66b861ab2b98c |
completed | June 21, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.