Triple
T19561016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Valentine |
E489448
|
entity |
| Predicate | chartedInCentury |
P136582
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Cape Valentine, chartedInCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chartedInCentury Context triple: [Cape Valentine, chartedInCentury, 19th century]
-
A.
endedInCentury
Indicates that an event, period, or process concluded during a specified century.
-
B.
revealedInCentury
Indicates that something became known, disclosed, or publicly revealed during a specified century.
-
C.
chartedIn
Indicates that something is recorded, mapped, or documented within a particular chart, diagram, or graphical representation.
-
D.
compiledInCentury
Indicates that something (such as a work, text, or document) was compiled during a specified century.
-
E.
discoveredInCentury
Indicates that an entity was discovered during a specific century.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63f7442e08190ad030151ec0a97d4 |
completed | April 20, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
| PDg | Predicate description generation | batch_69e51796b4c48190b721114dde654bd7 |
completed | April 19, 2026, 5:57 p.m. |
Created at: April 10, 2026, 1:42 p.m.