Triple
T8806407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JBuilder |
E209542
|
entity |
| Predicate | supportsBuildTool |
P19952
|
FINISHED |
| Object | Maven |
E72060
|
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: Maven | Statement: [JBuilder, supportsBuildTool, Maven]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maven Context triple: [JBuilder, supportsBuildTool, Maven]
-
A.
Maven
chosen
Maven is a widely used build automation and project management tool for Java-based software projects, known for its convention-over-configuration approach and dependency management.
-
B.
MAVEN
MAVEN is a NASA spacecraft mission designed to study the Martian upper atmosphere and its role in the planet’s climate evolution.
-
C.
Apache Ivy
Apache Ivy is a dependency management tool for Java projects that focuses on flexible configuration and integration with Apache Ant.
-
D.
Gradle
Gradle is a powerful, flexible build automation tool and dependency management system widely used in Java and other JVM-based projects.
-
E.
Apache Ant
Apache Ant is a Java-based build automation tool commonly used to compile, package, and deploy Java applications using XML build files.
- 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_69ca836320e48190b5cf585b90a322c4 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fd1f1a08190a2e584f6b0495f5c |
completed | March 31, 2026, 11:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf6f96bb448190b9316ad55d61662a |
completed | April 3, 2026, 7:43 a.m. |
Created at: March 30, 2026, 6:45 p.m.