Triple
T3418581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eclipse IDE |
E72064
|
entity |
| Predicate | supportsBuildSystem |
P13398
|
FINISHED |
| Object | Ant |
E72062
|
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: Ant | Statement: [Eclipse IDE, supportsBuildSystem, Ant]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ant Context triple: [Eclipse IDE, supportsBuildSystem, Ant]
-
A.
Ant
chosen
Ant is a Java-based build automation tool commonly used to compile, package, and deploy Java applications using XML configuration files.
-
B.
Anth
Anth is a familiar diminutive or nickname commonly used for the given name Anthony.
-
C.
Ath
Ath is a historic fortified town in the Wallonia region of Belgium, known for its medieval architecture and traditional annual festivals.
-
D.
AN
AN is the vehicle registration code used on license plates for the Ansbach district in the Middle Franconia region of Bavaria, Germany.
-
E.
AN
AN is the standard abbreviation for Anthropology News, a publication focused on current developments, research, and issues in the field of anthropology.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb92df1e48190bbf22a47e44579f1 |
completed | March 8, 2026, 6 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b367f369248190b411098b5654b8ad |
completed | March 13, 2026, 1:27 a.m. |
Created at: March 8, 2026, 3:15 p.m.