Triple
T3096865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sancio Cabot |
E64615
|
entity |
| Predicate | historicalEvidence |
P45898
|
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: [Sancio Cabot, historicalEvidence, sparsely documented]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEvidence Context triple: [Sancio Cabot, historicalEvidence, sparsely documented]
-
A.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
-
B.
historicalExistence
Indicates that an entity actually existed at some point in real-world history, as opposed to being fictional, hypothetical, or mythological.
-
C.
historicalExploration
Indicates that an entity has engaged in or is associated with the act of exploring or investigating something in the past.
-
D.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
-
E.
historicalPaper
Indicates that a paper has significant historical importance or impact within its field or context.
- 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_69ad857dc98481909e585dc3372e3ed5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada23cbe3c8190b7ec5cfd464a1ca8 |
completed | March 8, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ad9df06ed88190809f0683122caa5a |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:03 p.m.