Triple
T4948198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On the Fates of Famous Men |
E111101
|
entity |
| Predicate | includesHistoricalNarratives |
P6847
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [On the Fates of Famous Men, includesHistoricalNarratives, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesHistoricalNarratives Context triple: [On the Fates of Famous Men, includesHistoricalNarratives, true]
-
A.
containsNarrativeOf
chosen
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
-
B.
portraysHumanHistoryAs
Indicates that one entity represents or depicts human history in a particular way or from a specific perspective.
-
C.
hasHistoricalContext
Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
-
D.
usesRealHistoricalEvents
Indicates that the subject incorporates or is based on actual events that occurred in real history.
-
E.
historicalInterest
Indicates that one entity has a notable relevance, appeal, or significance to the study or understanding of 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd716520f08190862249efb2058fd4 |
completed | March 20, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:31 p.m.