Triple
T27001593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johanna de Jongh |
E680120
|
entity |
| Predicate | historicalDocumentationStatus |
P91820
|
FINISHED |
| Object | sparsely documented |
—
|
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: sparsely documented | Statement: [Johanna de Jongh, historicalDocumentationStatus, sparsely documented]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalDocumentationStatus Context triple: [Johanna de Jongh, historicalDocumentationStatus, sparsely documented]
-
A.
historicalStatusOf
Indicates the historical condition, role, or classification that an entity held during a specific past period or context.
-
B.
historiographicalStatus
Indicates the recognized standing or classification of something within historical writing or scholarship, such as how it is interpreted, debated, or valued by historians.
-
C.
historicalRecordStatus
Indicates the status or condition of a record within a historical or archival context (e.g., active, archived, revised, or obsolete).
-
D.
historicalDocumentationLevel
chosen
Indicates the extent or quality of recorded evidence or documentation available about a particular event, entity, or relationship.
-
E.
historicallyDocumentedBy
Indicates that information about an entity or event is recorded or attested in a specific historical document or source.
- 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: April 27, 2026, 6:57 a.m.