Triple
T15641586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pitman (namesake unknown) |
E376078
|
entity |
| Predicate | historicalInformation |
P43371
|
FINISHED |
| Object | not widely 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: not widely documented | Statement: [Pitman (namesake unknown), historicalInformation, not widely documented]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalInformation Context triple: [Pitman (namesake unknown), historicalInformation, not widely documented]
-
A.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
-
B.
historicalBackground
chosen
Indicates that one entity provides contextual historical information or circumstances that help explain the origin, development, or significance of another entity.
-
C.
historicalInterest
Indicates that one entity has a notable relevance, appeal, or significance to the study or understanding of the past.
-
D.
historicallyRich
Indicates that an entity possesses significant historical depth, importance, or a wealth of notable past events and heritage.
-
E.
historicalSee
Indicates that one entity observed, encountered, or took visual notice of another entity in the past.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ed23d688190bea996f90989d406 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.