Triple
T36172170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miles Adler-Hart |
E1046172
|
entity |
| Predicate | hasPointOfViewIn |
P8789
|
FINISHED |
| Object | Casebook |
—
|
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: Casebook | Statement: [Miles Adler-Hart, hasPointOfViewIn, Casebook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPointOfViewIn Context triple: [Miles Adler-Hart, hasPointOfViewIn, Casebook]
-
A.
hasViewingPointFor
Indicates that one entity serves as a vantage point or location from which another entity can be viewed or observed.
-
B.
hasViewpointType
Indicates that something is associated with or characterized by a particular type or category of viewpoint or perspective.
-
C.
hasFieldOfView
Indicates that one entity possesses a visual coverage area within which it can perceive or detect other entities or regions.
-
D.
perspectiveOf
chosen
Indicates that something is expressed, depicted, or understood from the viewpoint or standpoint of a particular entity.
-
E.
hasViewpointConcept
Indicates that something is associated with, characterized by, or defined through a particular viewpoint, perspective, or conceptual stance.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: May 3, 2026, 4:08 p.m.