Triple
T25426479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FH10 |
E637128
|
entity |
| Predicate | nativeApplication |
P159121
|
FINISHED |
| Object | Macromedia FreeHand for Windows |
—
|
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: Macromedia FreeHand for Windows | Statement: [FH10, nativeApplication, Macromedia FreeHand for Windows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeApplication Context triple: [FH10, nativeApplication, Macromedia FreeHand for Windows]
-
A.
nativeApplication
chosen
Indicates that an application is specifically designed to run directly on a particular platform or operating system, using its native runtime and capabilities.
-
B.
exampleApplication
Indicates that something serves as a representative or illustrative instance of how an application is used or functions.
-
C.
surfaceApplication
Indicates that a substance, treatment, or process is applied to the outer surface of an object or material.
-
D.
aplicación
Indicates that one entity is the use or implementation of another entity for a specific purpose or function.
-
E.
definesApplication
Indicates that one entity specifies or establishes the purpose, scope, or behavior of an application associated with another entity.
- 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_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_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 1:57 p.m.