Triple
T25426453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FH9 |
E637127
|
entity |
| Predicate | fileTypeFamily |
P159120
|
FINISHED |
| Object | FreeHand file format |
—
|
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: FreeHand file format | Statement: [FH9, fileTypeFamily, FreeHand file format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fileTypeFamily Context triple: [FH9, fileTypeFamily, FreeHand file format]
-
A.
fileTypeCode
Indicates the specific classification or category code that identifies the type or format of a file.
-
B.
filenameType
Indicates the type or category associated with a given filename (e.g., file format, role, or classification).
-
C.
typicalFileType
Indicates that one entity is the usual or commonly associated file type for the other entity.
-
D.
fileSystemFamily
Indicates that two file systems belong to the same family or type, sharing a common design, lineage, or implementation characteristics.
-
E.
fileTypeIIDMeaning
Indicates that the predicate specifies the meaning or interpretation associated with a particular file type identifier (IID).
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6bfdb748190abfd40ed1838d9aa |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 1:57 p.m.