Triple
T27946035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PredictionEngine |
E700880
|
entity |
| Predicate | hasGenericTypeParameter |
P163132
|
FINISHED |
| Object | TData |
—
|
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: TData | Statement: [PredictionEngine, hasGenericTypeParameter, TData]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenericTypeParameter Context triple: [PredictionEngine, hasGenericTypeParameter, TData]
-
A.
hasParameterType
Indicates that a parameter in a function, method, or operation is associated with a specific data type.
-
B.
isGenericType
chosen
Indicates that one entity is a type definition or instance that is parameterized by one or more type parameters (i.e., a generic type).
-
C.
genericTypeParameterCount
Indicates the number of generic type parameters associated with a given type, method, or construct.
-
D.
isGenericOver
Indicates that one entity is defined or parameterized in terms of another, more specific entity, such that it can operate over or apply to that entity as a generic.
-
E.
hasGenericName
Indicates that an entity is associated with a non-brand, generic name that designates its general type or class.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 7:22 p.m.