Triple
T26966604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EXPTIME |
E679188
|
entity |
| Predicate | believedToBeProperSupersetOf |
P163079
|
FINISHED |
| Object | P |
—
|
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: P | Statement: [EXPTIME, believedToBeProperSupersetOf, P]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: believedToBeProperSupersetOf Context triple: [EXPTIME, believedToBeProperSupersetOf, P]
-
A.
areSupersetOf
Indicates that one set contains all elements of another set, possibly along with additional elements.
-
B.
hasSubset
Indicates that one set is entirely contained within another set, with all elements of the first set also belonging to the second.
-
C.
isSupergroupOf
Indicates that one group contains another group as a proper subgroup, having strictly more members or elements than the other.
-
D.
canonicalSetIncludes
Indicates that a canonical or standard set contains the referenced element as one of its members.
-
E.
isUpperBoundFor
Indicates that one value is greater than or equal to every element in a given set or collection, serving as an upper limit for them.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f63639a84c81909d700a539b458b42 |
completed | May 2, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 6:36 a.m.