Triple
T12899281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | e-TeX |
E308573
|
entity |
| Predicate | hasPrimitive |
P107341
|
FINISHED |
| Object | umexpr |
—
|
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: umexpr | Statement: [e-TeX, hasPrimitive, umexpr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimitive Context triple: [e-TeX, hasPrimitive, umexpr]
-
A.
usesPrimitiveType
Indicates that one entity employs or relies on a specified primitive data type in its definition or implementation.
-
B.
hasPrimitiveRelation
Indicates a basic, direct relationship between entities that is not derived from or dependent on any other relations.
-
C.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
D.
isPrimaryTypeAvailable
Indicates whether a primary or main type associated with an entity is currently available or defined.
-
E.
hasPrimaryFeature
Indicates that an entity possesses a main or most characteristic feature that defines or distinguishes it.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9717f3fc48190b61c8f6f36cd0725 |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9713e45a88190acd346f066093550 |
completed | April 10, 2026, 9:53 p.m. |
Created at: April 9, 2026, 5:40 p.m.