Triple
T36598397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MapBasic |
E902857
|
entity |
| Predicate | hasSyntaxSimilarTo |
P186062
|
FINISHED |
| Object | BASIC family languages |
—
|
NE NERFINISHED |
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: BASIC family languages | Statement: [MapBasic, hasSyntaxSimilarTo, BASIC family languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSyntaxSimilarTo Context triple: [MapBasic, hasSyntaxSimilarTo, BASIC family languages]
-
A.
hasSimilarityTo
Indicates that one entity shares common characteristics, features, or qualities with another entity to a notable degree.
-
B.
hasLexicalSimilarityWith
Indicates that two linguistic items share a significant degree of similarity in form, structure, or wording.
-
C.
hasGrammaticalSimilarityTo
Indicates that two linguistic elements share similar grammatical structure, form, or function.
-
D.
hasLanguageSimilarTo
Indicates that one entity uses or is associated with a language that is similar or closely related to the language used or associated with another entity.
-
E.
hasSyntaxInfluenceFrom
Indicates that the syntax of one entity is influenced, shaped, or derived from the syntax of another entity.
- F. None of above. chosen
Provenance (4 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:11 p.m.