Triple
T14439069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JavaCC |
E358039
|
entity |
| Predicate | JJTreeFunction |
P114278
|
FINISHED |
| Object | syntax tree generation |
—
|
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: syntax tree generation | Statement: [JavaCC, JJTreeFunction, syntax tree generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: JJTreeFunction Context triple: [JavaCC, JJTreeFunction, syntax tree generation]
-
A.
leafFunction
Indicates that something serves as a terminal or non-decomposable function within a larger functional or computational structure.
-
B.
PLEXFunction
Indicates a functional or operational role that one entity performs or serves for another within a system or context.
-
C.
jawFunction
Indicates the functional role, movement, or mechanical action performed by a jaw in relation to other anatomical structures or processes.
-
D.
LFunctionType
Indicates that one entity is a function whose type or signature is characterized, constrained, or defined by the other entity.
-
E.
commonTreeType
Indicates that two or more entities share the same type or classification of tree.
- 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_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. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:18 a.m.