Triple
T29867358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DWF |
E758492
|
entity |
| Predicate | viewerApplication |
P168204
|
FINISHED |
| Object | Autodesk Design Review |
—
|
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: Autodesk Design Review | Statement: [DWF, viewerApplication, Autodesk Design Review]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewerApplication Context triple: [DWF, viewerApplication, Autodesk Design Review]
-
A.
viewIs
Indicates that one entity is a visual representation or perspective of another entity.
-
B.
viewerInteraction
Indicates that one entity engages with or responds to content presented by another entity, such as by viewing, reacting, or otherwise interacting with it.
-
C.
viewOver
Indicates that one entity has a visual perspective overlooking or facing another entity, typically providing a vantage point onto it.
-
D.
viewTechnology
Indicates that an entity observes, inspects, or examines a particular technology.
-
E.
viewTechnologyIn
Indicates that a technology is being viewed, examined, or accessed within a particular context, location, or environment.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6768a6b348190a88b3aa787249cb3 |
completed | May 2, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 5:52 p.m.