Triple
T26991107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JUnit |
E679861
|
entity |
| Predicate | typicalAnnotation |
P199537
|
FINISHED |
| Object | @Test |
—
|
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: @Test | Statement: [JUnit, typicalAnnotation, @Test]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAnnotation Context triple: [JUnit, typicalAnnotation, @Test]
-
A.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
B.
typicalSymbol
Indicates that something serves as a characteristic or commonly recognized symbol representing something else.
-
C.
notatedWith
Indicates that something is represented, marked, or written using a particular system of notation or symbols.
-
D.
typicalDesignation
Indicates that one entity is the usual or commonly used designation (name, label, or title) for another entity.
-
E.
typicalProperty
Indicates that a certain property is characteristically or commonly associated with an entity, reflecting what is typical for that entity.
- F. None of above. chosen
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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff41645c548190b7cb4e53079b93ef |
completed | May 9, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69ff410aa33c8190869ba769ac2a93ce |
completed | May 9, 2026, 2:13 p.m. |
| PDg | Predicate description generation | batch_69ff4163a8548190b0eaafd0a377b141 |
completed | May 9, 2026, 2:14 p.m. |
Created at: April 27, 2026, 6:51 a.m.