Triple
T3205514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broussonetia |
E67150
|
entity |
| Predicate | fiberSourceFor |
P409
|
FINISHED |
| Object | traditional East Asian 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: traditional East Asian paper | Statement: [Broussonetia, fiberSourceFor, traditional East Asian paper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fiberSourceFor Context triple: [Broussonetia, fiberSourceFor, traditional East Asian paper]
-
A.
genomeSource
Indicates the origin or provenance of a genome, specifying where or how the genomic data was obtained.
-
B.
source
chosen
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
C.
doctrineSourceFor
Indicates that one entity serves as the originating basis or authoritative source of doctrine, teachings, or principles for another entity.
-
D.
fiberContent
Indicates that one entity specifies the amount or presence of dietary fiber contained in another entity.
-
E.
usesSourceType
Indicates that one entity makes use of, relies on, or operates based on a particular type or category of source.
- 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaa559848819082d1e61f586278dd |
completed | March 8, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69ad9e078f7c8190813d9fcb4f5071fb |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.