Triple
T35103301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | upLaTeX |
E1013078
|
entity |
| Predicate | supportsDocumentClass |
—
|
GENERATED |
| Object | jsarticle |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDocumentClass Context triple: [upLaTeX, supportsDocumentClass, jsarticle]
-
A.
supportsDocument
Indicates that one entity provides compatibility or functionality for handling, processing, or using a particular document or document type.
-
B.
supportedClass
chosen
Indicates that one entity is a class or type that is recognized, handled, or operable within the capabilities or context provided by another entity.
-
C.
supportsClassification
Indicates that one entity provides the capability or functionality needed for another entity to perform or maintain a specific classification.
-
D.
hasDocumentClass
Indicates that an entity is associated with, or categorized under, a specific class or type of document.
-
E.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
- F. None of above.
Provenance (1 batch)
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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.