Triple
T498317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALGOL W |
E10343
|
entity |
| Predicate | hasSyntaxStyle |
P5327
|
FINISHED |
| Object | ALGOL-like block structure |
—
|
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: ALGOL-like block structure | Statement: [ALGOL W, hasSyntaxStyle, ALGOL-like block structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSyntaxStyle Context triple: [ALGOL W, hasSyntaxStyle, ALGOL-like block structure]
-
A.
hasStyle
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
B.
hasSubstyle
Indicates that one style is a more specific or subordinate variant of another style within a hierarchical style structure.
-
C.
hasStyleGuide
Indicates that one entity is associated with or governed by a particular style guide that defines its formatting or presentation conventions.
-
D.
hasHigherStyleThan
Indicates that one entity’s style is considered superior or more fashionable than another’s.
-
E.
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.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1183e988190bce70932a9678134 |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edfa87cc8190a77c726a5a55b7d9 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.