Triple
T34954726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hàn Thế Thành |
E1008095
|
entity |
| Predicate | softwareAuthored |
P145344
|
FINISHED |
| Object | pdfTeX |
—
|
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: pdfTeX | Statement: [Hàn Thế Thành, softwareAuthored, pdfTeX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareAuthored Context triple: [Hàn Thế Thành, softwareAuthored, pdfTeX]
-
A.
developedSoftware
chosen
Indicates that one entity created, programmed, or significantly contributed to the creation of a particular software system or application for another entity or purpose.
-
B.
softwareEngine
Indicates that an entity functions as a software engine, i.e., a core computational or processing component that drives or powers software operations for another entity.
-
C.
softwareTypePublished
Indicates that a particular type or category of software has been officially released or made publicly available.
-
D.
hasProgrammingFrom
Indicates that something derives its programming, configuration, or behavioral instructions from a specified source.
-
E.
softwareFor
Indicates that one entity is designed, intended, or used to operate on, support, or be compatible with another entity as software.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.