Triple
T30418254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Further Up the Road |
E773817
|
entity |
| Predicate | hasPageContentType |
P640
|
FINISHED |
| Object | photographs |
—
|
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: photographs | Statement: [Further Up the Road, hasPageContentType, photographs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPageContentType Context triple: [Further Up the Road, hasPageContentType, photographs]
-
A.
hasContentType
chosen
Indicates that an entity is associated with or classified by a specific type of content.
-
B.
hasPage
Indicates that one entity includes, is associated with, or is documented by a specific page (such as a web page or document page).
-
C.
governsContentType
Indicates that one entity defines or controls the rules, behavior, or handling associated with a particular content type.
-
D.
hasInteriorContentType
Indicates that something contains internal material or content of a specified type.
-
E.
hasPageRange
Indicates that one entity (such as a document section or article) spans a specific, continuous range of pages in another entity (such as a publication or volume).
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
Created at: April 29, 2026, 8:05 p.m.