Triple
T32385352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 小篆 |
E827531
|
entity |
| Predicate | 被谁整理 |
P5107
|
FINISHED |
| Object | 李斯 |
—
|
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: 李斯 | Statement: [小篆, 被谁整理, 李斯]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 被谁整理 Context triple: [小篆, 被谁整理, 李斯]
-
A.
organizedBySince
Indicates that an entity has been organized by a particular organizer starting from a specified point in time and continuing from then onward.
-
B.
organizedFrom
Indicates that something has been arranged, structured, or formed starting from a specified source or initial set of elements.
-
C.
laterReorganizedBy
Indicates that an entity was subsequently restructured, reorganized, or reformed by another entity at a later time.
-
D.
curatedBy
chosen
Indicates that something has been selectively organized, managed, or assembled by a particular agent or entity.
-
E.
reorganizedFor
Indicates that one entity has been rearranged, restructured, or otherwise modified in its organization for the benefit, use, or requirements of another entity.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1cf2aa081909f4c0b8f0cad1907 |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:51 a.m.