Triple
T16237812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Biographer’s Tale |
E394159
|
entity |
| Predicate | exploresBoundaryBetween |
P122282
|
FINISHED |
| Object | biography and fiction |
—
|
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: biography and fiction | Statement: [The Biographer’s Tale, exploresBoundaryBetween, biography and fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploresBoundaryBetween Context triple: [The Biographer’s Tale, exploresBoundaryBetween, biography and fiction]
-
A.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
B.
onBorderBetween
Indicates that an entity is located along or directly adjacent to the dividing line shared by two distinct regions or areas.
-
C.
borderPoint
Indicates a point that lies on the boundary between two regions or entities.
-
D.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
E.
nearBorderBetween
Indicates that something is located close to the dividing line or boundary shared between two adjacent areas or regions.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2455bb23881909c4cb4c1439d2bc5 |
completed | April 17, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:04 a.m.