Triple
T32414703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gremlin API |
E828307
|
entity |
| Predicate | hasSyntaxForm |
P169
|
FINISHED |
| Object | Groovy-based DSL |
—
|
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: Groovy-based DSL | Statement: [Gremlin API, hasSyntaxForm, Groovy-based DSL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSyntaxForm Context triple: [Gremlin API, hasSyntaxForm, Groovy-based DSL]
-
A.
hasFormOfRule
Indicates that one entity embodies, expresses, or takes the specific form of a rule defined by another entity.
-
B.
hasForm
chosen
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
-
C.
hasSyntaxKeyword
Indicates that an element or construct is associated with, or marked by, a specific keyword in the syntax of a language or formal system.
-
D.
hasSymbolicForm
Indicates that one entity serves as the symbolic representation or abstract form of another entity.
-
E.
hasFormFor
Indicates that one entity possesses or provides a specific form or document intended to be used by another entity or for a particular purpose.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c25bb38881909a5a0552b316e970 |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:53 a.m.