Triple
T31646819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System F |
E807603
|
entity |
| Predicate | hasTypeConstructor |
P197594
|
FINISHED |
| Object | universal type (forall type) |
—
|
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: universal type (forall type) | Statement: [System F, hasTypeConstructor, universal type (forall type)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeConstructor Context triple: [System F, hasTypeConstructor, universal type (forall type)]
-
A.
hasConstructorType
Indicates that an entity is associated with, or defined by, a specific type of constructor (e.g., a particular construction method, pattern, or signature).
-
B.
hasConstructor
Indicates that an entity defines or is associated with a specific constructor used to create or initialize instances of it.
-
C.
hasTypeParameter
Indicates that one entity is defined with a type parameter that is represented or referenced by the other entity.
-
D.
hasTypeChecker
Indicates that an entity is associated with or utilizes a specific type checker component or mechanism.
-
E.
hasRuntimeType
Indicates that an entity is of, or conforms to, a specific type when evaluated at runtime rather than at compile time.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe9dfaa2d08190b2084f63f842eb6b |
completed | May 9, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69fe9bba947c81908b0b2b92a4d19b37 |
completed | May 9, 2026, 2:28 a.m. |
| PDg | Predicate description generation | batch_69fe9df9561c8190a068f91c9fc78e56 |
completed | May 9, 2026, 2:37 a.m. |
Created at: April 30, 2026, 10:51 p.m.