Triple
T32385388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 小篆 |
E827531
|
entity |
| Predicate | 相关著名作品 |
P168847
|
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.
notableFeatureOfWork
Indicates that a particular feature, characteristic, or aspect is a notable or distinguishing element of a given work.
-
B.
notableWorkWith
Indicates a relationship where two or more entities are recognized for having collaborated on or been jointly associated with a significant work or project.
-
C.
isFamousWorkOf
chosen
Indicates that one entity is a well-known or widely recognized work created by another entity (typically an artist, author, or creator).
-
D.
notableWorkContained
Indicates that a notable work is included within or is part of another entity, such as a collection, publication, or compilation.
-
E.
notableWorkFeaturing
Indicates that a particular notable work (such as a book, film, or artwork) prominently includes, showcases, or is centered around a given 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.