Triple
T14439842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Velocity templates |
E358056
|
entity |
| Predicate | contextContains |
P95472
|
FINISHED |
| Object | Java objects |
—
|
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: Java objects | Statement: [Velocity templates, contextContains, Java objects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contextContains Context triple: [Velocity templates, contextContains, Java objects]
-
A.
contextHolds
Indicates that a particular contextual condition or situation is valid and in effect for the related entities or statements.
-
B.
typicallyContain
chosen
Indicates that one entity is normally or commonly found within, included in, or held by another entity under usual circumstances.
-
C.
contextOf
Indicates that one entity provides the situational, informational, or environmental background within which another entity exists, occurs, or is interpreted.
-
D.
context
Indicates that one entity provides the surrounding circumstances, setting, or background within which another entity, event, or statement occurs or is interpreted.
-
E.
containedWith
Indicates that one entity is located or kept inside the bounds or interior space of another entity.
- 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_69de914c1398819090fa2a74d257ba3e |
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.