Triple
T14439065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JavaCC |
E358039
|
entity |
| Predicate | supportsRegularExpressions |
P29142
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [JavaCC, supportsRegularExpressions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRegularExpressions Context triple: [JavaCC, supportsRegularExpressions, true]
-
A.
supportsPartialMatch
Indicates that the relationship or operation allows matching based on a subset or portion of the target criteria rather than requiring a complete or exact match.
-
B.
supportsExactMatch
Indicates that one entity fully upholds or is compatible with another entity only when there is an exact, unaltered match between them.
-
C.
supportsPatternType
chosen
Indicates that one entity is compatible with, or capable of handling, a specified pattern type.
-
D.
supportsMultipleMatches
Indicates that the relationship or operation can involve or return more than one matching counterpart rather than being limited to a single match.
-
E.
supportsEscapeSequences
Indicates that an entity can recognize and correctly process escape sequence characters within its input or content.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de914a45ec81909ab8ccf302047d7f |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.