Triple
T27766671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hànshū |
E701618
|
entity |
| Predicate | includesContributionsBy |
P30146
|
FINISHED |
| Object | Ban Zhao |
—
|
NE NERFINISHED |
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: Ban Zhao | Statement: [Hànshū, includesContributionsBy, Ban Zhao]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesContributionsBy Context triple: [Hànshū, includesContributionsBy, Ban Zhao]
-
A.
hasContributionFrom
chosen
Indicates that something (such as a work, project, or outcome) is created, influenced, or supported in part by a specified contributor.
-
B.
showsContributionTo
Indicates that one entity demonstrates, reveals, or provides evidence of another entity’s contribution to something.
-
C.
acceptsContributions
Indicates that an entity receives or allows contributions (such as funds, content, or resources) from other entities.
-
D.
contributionBased
Indicates that something is determined, allocated, or structured according to the level or amount of contributions made by the involved entities.
-
E.
contributionBase
Indicates the foundational amount, value, or resource on which a contribution, payment, or benefit is calculated or determined.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: April 27, 2026, 4:31 p.m.