Triple
T26966634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EXPTIME |
E679188
|
entity |
| Predicate | formalNotation |
P165377
|
FINISHED |
| Object | EXPTIME |
—
|
NE NERFINISHED |
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: EXPTIME | Statement: [EXPTIME, formalNotation, EXPTIME]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalNotation Context triple: [EXPTIME, formalNotation, EXPTIME]
-
A.
typicalNotation
Indicates that one entity is the standard or commonly used symbolic representation (notation) for another entity.
-
B.
informalNotation
Indicates that an entity is represented or expressed using a non-standard, simplified, or colloquial form of notation rather than a formal or fully rigorous one.
-
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.
sequenceNotation
Indicates that one entity specifies the ordered symbolic representation (notation) used to express a sequence associated with another entity.
- 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_69f658a91ba0819084fbe3dd8a09f7cd |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f657f2c8b08190bfeb3173ef78207d |
completed | May 2, 2026, 8 p.m. |
Created at: April 27, 2026, 6:36 a.m.