Triple
T14168571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 伊藤 清 |
E351143
|
entity |
| Predicate | 業績 |
P20732
|
FINISHED |
| Object | 伊藤積分の創始 |
—
|
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: 伊藤積分の創始 | Statement: [伊藤 清, 業績, 伊藤積分の創始]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 業績 Context triple: [伊藤 清, 業績, 伊藤積分の創始]
-
A.
業績の影響
Indicates that one entity’s performance or results have an effect on, or bring about changes in, another entity or outcome.
-
B.
performanceWith
Indicates a relationship where two or more entities participate together in the same performance or staged presentation.
-
C.
performanceBasis
Indicates that one entity’s performance is evaluated, determined, or justified on the basis of another specified factor, standard, or reference.
-
D.
salesPerformance
Indicates how effectively an entity achieves its sales objectives, typically measured by revenue, volume, or growth over a given period.
-
E.
notableWorkPerformed
chosen
Indicates that an entity has created, executed, or contributed significantly to a particular work that is recognized as notable or important.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b355f08190864c7322bbcb766d |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1 a.m.