Triple
T29012435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AppleSoft BASIC PDL function |
E736601
|
entity |
| Predicate | argumentRange |
P27293
|
FINISHED |
| Object | 0–3 |
—
|
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: 0–3 | Statement: [AppleSoft BASIC PDL function, argumentRange, 0–3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: argumentRange Context triple: [AppleSoft BASIC PDL function, argumentRange, 0–3]
-
A.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
B.
hasRange
chosen
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
C.
rangeVariant
Indicates that one entity is a variant or alternative form within the value range defined or covered by another entity.
-
D.
testRange
Indicates that a value, condition, or behavior is being evaluated to determine whether it falls within a specified range or interval.
-
E.
argumentCount
Indicates the number of arguments that a function, method, or callable entity takes.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fdd91dc8190a627a1a4fd65dfc0 |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 9:43 a.m.