Triple
T400729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABC programming language |
E9273
|
entity |
| Predicate | hasSyntaxCharacteristic |
P5192
|
FINISHED |
| Object | indentation-based blocks |
—
|
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: indentation-based blocks | Statement: [ABC programming language, hasSyntaxCharacteristic, indentation-based blocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSyntaxCharacteristic Context triple: [ABC programming language, hasSyntaxCharacteristic, indentation-based blocks]
-
A.
hasLinguisticFeature
Indicates that an entity possesses a particular linguistic property, trait, or characteristic.
-
B.
hasSpecialCharacter
Indicates that a given entity (such as a string or identifier) contains at least one non-alphanumeric special character.
-
C.
languageFeature
chosen
Indicates that one entity is a characteristic, property, or capability of a language associated with the other entity.
-
D.
hasCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
E.
syntaxBasedOn
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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ec8e655c819081eff85c0ef55fa5 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96ee4ec8190a5c0e3f491d3963d |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.