Triple
T6242261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sutsilvan |
E139631
|
entity |
| Predicate | historicalDocumentsFrom |
P45898
|
FINISHED |
| Object | early modern period |
—
|
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: early modern period | Statement: [Sutsilvan, historicalDocumentsFrom, early modern period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalDocumentsFrom Context triple: [Sutsilvan, historicalDocumentsFrom, early modern period]
-
A.
historicallyDocumentedBy
Indicates that information about an entity or event is recorded or attested in a specific historical document or source.
-
B.
historicalEvidence
chosen
Indicates that there exists documented or otherwise verifiable information supporting the occurrence, authenticity, or truth of a past event, state, or relationship between entities.
-
C.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of another entity.
-
D.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
-
E.
historicalPaper
Indicates that a paper has significant historical importance or impact within its field or context.
- 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_69c008b1c5088190ae6de2555fc05ad8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0631933488190838b424ec0fc2155 |
completed | March 22, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c056037bf88190a0a3fe7429345d0b |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:23 p.m.