Triple
T27560327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pandoc |
E695751
|
entity |
| Predicate | supportsMathFormat |
P85212
|
FINISHED |
| Object | LaTeX math |
—
|
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: LaTeX math | Statement: [Pandoc, supportsMathFormat, LaTeX math]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMathFormat Context triple: [Pandoc, supportsMathFormat, LaTeX math]
-
A.
supportsTextFormat
chosen
Indicates that one entity is capable of handling, rendering, or otherwise working with a specified text format.
-
B.
supportsArbitraryPrecisionArithmetic
Indicates that the subject system or component can perform arithmetic operations with numbers of virtually unlimited size and precision, beyond fixed hardware-imposed limits.
-
C.
supportsMathematicsTopic
Indicates that one entity provides assistance, resources, or reinforcement for understanding or working with a particular mathematics topic.
-
D.
supportsFloatingPoint
Indicates that an entity is capable of handling or operating with floating-point (non-integer) numeric values.
-
E.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
- F. None of above.
Provenance (3 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
Created at: April 27, 2026, 1:38 p.m.