Triple
T36488900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2.5D sketch |
E899003
|
entity |
| Predicate | viewDependence |
P62492
|
FINISHED |
| Object | view-dependent representation |
—
|
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: view-dependent representation | Statement: [2.5D sketch, viewDependence, view-dependent representation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewDependence Context triple: [2.5D sketch, viewDependence, view-dependent representation]
-
A.
viewIs
Indicates that one entity is a visual representation or perspective of another entity.
-
B.
viewResponsibility
Indicates that one entity has the authority or obligation to view or access information or resources associated with another entity.
-
C.
observerDependent
Indicates that the truth, value, or manifestation of something varies depending on which observer is considering or measuring it.
-
D.
viewsBehaviorAs
Indicates that one entity interprets, judges, or regards another entity’s behavior in a particular way.
-
E.
representationDependsOn
chosen
Indicates that one representation is reliant on or derived from another representation in order to be valid, complete, or interpretable.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.