Triple
T32991501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | area theorem |
E844098
|
entity |
| Predicate | notApplicableIn |
P7029
|
FINISHED |
| Object | full quantum gravity |
—
|
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: full quantum gravity | Statement: [area theorem, notApplicableIn, full quantum gravity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notApplicableIn Context triple: [area theorem, notApplicableIn, full quantum gravity]
-
A.
notAvailableFor
Indicates that an entity is currently not accessible, usable, or eligible for a particular action, purpose, or association.
-
B.
notUsedInCountry
Indicates that a given item, resource, or entity is not utilized, applied, or in operation within a specified country.
-
C.
doesNotGenerallyApplyTo
chosen
Indicates that a rule, property, or condition is typically not relevant or applicable to the referenced entity or situation in most cases.
-
D.
notUsedInRegion
Indicates that something is not utilized, applied, or present within a specified geographic or administrative region.
-
E.
notDirectlyAvailableFor
Indicates that an entity cannot be accessed, used, or obtained immediately or without intermediaries, but may be reachable through indirect means or additional steps.
- 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d213a4148190862c180ce546494a |
completed | May 3, 2026, 4:41 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:22 a.m.