Triple
T35103305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | upLaTeX |
E1013078
|
entity |
| Predicate | typicalInvocationCommand |
P101150
|
FINISHED |
| Object | uplatex |
E1013078
|
NE 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: uplatex | Statement: [upLaTeX, typicalInvocationCommand, uplatex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalInvocationCommand Context triple: [upLaTeX, typicalInvocationCommand, uplatex]
-
A.
typicalInvocations
Indicates the usual or most common ways in which an action, function, or process is called, used, or carried out.
-
B.
typicalCommands
Indicates that the associated entity commonly issues or uses the specified commands as part of its normal or expected behavior.
-
C.
typicalCommandLine
chosen
Indicates that one entity represents the usual or standard command-line invocation or syntax associated with another entity.
-
D.
typicalCommandLevel
Indicates the usual or standard level of authority or access at which a command is intended to be executed.
-
E.
invocationOf
Indicates that one entity is the act, event, or instance of calling upon, summoning, or appealing to another entity (such as a function, service, or authority) to perform its role or be brought into effect.
- F. None of above.
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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37cff8e25c8190bd1bc4a930842eed |
completed | June 21, 2026, 11:50 a.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.