Triple
T36872286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ParamSpec |
E911253
|
entity |
| Predicate | isVariadic |
P74944
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [ParamSpec, isVariadic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVariadic Context triple: [ParamSpec, isVariadic, true]
-
A.
hasVariableLength
chosen
Indicates that the related entity can vary in size, duration, or extent rather than having a fixed, constant length.
-
B.
hasVariability
Indicates that an entity exhibits variation or fluctuation in its state, value, or characteristics over time or across instances.
-
C.
isNonPositional
Indicates that the relationship or property does not depend on the specific position, order, or location of the entities involved.
-
D.
hasVariance
Indicates that there is a measurable degree of variability or dispersion in the values or outcomes associated with the related entities.
-
E.
containsVariableStars
Indicates that the subject includes one or more stars whose brightness changes over time (variable stars).
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.