Triple
T815625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algol 68 |
E17646
|
entity |
| Predicate | hasSyntax |
P5327
|
FINISHED |
| Object | two-level grammar (van Wijngaarden grammar) |
—
|
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: two-level grammar (van Wijngaarden grammar) | Statement: [Algol 68, hasSyntax, two-level grammar (van Wijngaarden grammar)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSyntax Context triple: [Algol 68, hasSyntax, two-level grammar (van Wijngaarden grammar)]
-
A.
hasKnownGrammar
Indicates that an entity is associated with a grammar whose structure and rules are already defined or understood.
-
B.
syntaxBasedOn
chosen
Indicates that the syntactic structure or rules of one entity are derived from, influenced by, or constructed according to the syntax of another entity.
-
C.
hasBracket
Indicates that one entity possesses, includes, or is associated with a bracket component or structure.
-
D.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
E.
hasDistinctGrammar
Indicates that the subject’s grammar system is different in structure or rules from that of the object.
- 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_69a4937bcaac8190a322524ac6f45a5a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab5157b08190b6c8f2fd455f261e |
completed | March 1, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69a4aa756920819080ae82948974c876 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.