Triple
T23791204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System F |
E588093
|
entity |
| Predicate | hasTypicalNotation |
P4882
|
FINISHED |
| Object | ∀α. τ for universal type quantification |
—
|
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: ∀α. τ for universal type quantification | Statement: [System F, hasTypicalNotation, ∀α. τ for universal type quantification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalNotation Context triple: [System F, hasTypicalNotation, ∀α. τ for universal type quantification]
-
A.
typicalNotation
chosen
Indicates that one entity is the standard or commonly used symbolic representation (notation) for another entity.
-
B.
hasAlternativeNotation
Indicates that an entity can be represented or written in a different, equivalent form or notation.
-
C.
appearsInNotation
Indicates that one entity is represented, referenced, or depicted within the formal notation or symbolic system associated with another entity.
-
D.
distinguishingNotation
Indicates that one entity uses a specific notation or symbol to distinguish or differentiate another entity from similar ones.
-
E.
usesNotationFor
Indicates that one entity employs or adopts a particular notation system or symbolic representation for another entity.
- 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_69e2490f4ad48190b690878eec3596c6 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c6d8215c8190af4f2dd7478e2c04 |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:17 p.m.