Triple
T1603625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Han dynasty |
E34448
|
entity |
| Predicate | majorInvention |
P14232
|
FINISHED |
| Object | paper |
—
|
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: paper | Statement: [Han dynasty, majorInvention, paper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorInvention Context triple: [Han dynasty, majorInvention, paper]
-
A.
inventionType
Indicates the specific category or kind of invention that characterizes the relationship between an invention and its type.
-
B.
wasInventedBy
Indicates that something (typically an object, concept, or process) was created or brought into existence by a particular inventor or originator.
-
C.
notableInventor
Indicates that the subject is a well-known or historically significant inventor of the object.
-
D.
technologyPioneered
chosen
Indicates that an entity was the first or among the first to develop, introduce, or significantly advance a particular technology.
-
E.
notableContribution
Indicates that an entity has made a significant, recognized contribution to another entity, field, work, or endeavor.
- 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_69a885fea6a481909fe83ba6441f1774 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a95b02cd448190be8e3db9a5a7bac0 |
completed | March 5, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69a907c1cad08190b9728dd557f39aa0 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.