Triple
T23791178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System F |
E588093
|
entity |
| Predicate | hasQuantificationLevel |
P20230
|
FINISHED |
| Object | second-order |
—
|
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: second-order | Statement: [System F, hasQuantificationLevel, second-order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuantificationLevel Context triple: [System F, hasQuantificationLevel, second-order]
-
A.
usesQuantification
Indicates that one entity employs or applies a system of quantification (such as numerical or measurable assessment) to another entity or context.
-
B.
quantificationType
chosen
Indicates the specific kind or category of quantity or measurement being applied in a given context.
-
C.
quantifiesOver
Indicates that one entity expresses a quantity, measurement, or numerical specification that applies to or ranges over another entity.
-
D.
hasObservationLevel
Indicates the degree, intensity, or extent to which something is observed, monitored, or measured within a given context.
-
E.
quantifies
Indicates that one entity expresses or specifies the amount, number, or degree of 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.