Triple
T426986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lei Yixin |
E9629
|
entity |
| Predicate | hasCreated |
P10499
|
FINISHED |
| Object | public sculptures in China |
—
|
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: public sculptures in China | Statement: [Lei Yixin, hasCreated, public sculptures in China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCreated Context triple: [Lei Yixin, hasCreated, public sculptures in China]
-
A.
hasCreation
chosen
Indicates a relationship where one entity is the creator or originator of another entity.
-
B.
createdIn
Indicates that one entity was brought into existence, produced, or originated within the context, location, or time frame specified by another entity.
-
C.
createdFor
Indicates that one entity was made, produced, or designed specifically to serve, benefit, or be used by another entity.
-
D.
hasInitial
Indicates that one entity possesses or is associated with the first letter or starting character of another entity’s name or value.
-
E.
createdAfterEvent
Indicates that the creation of one entity occurred after a specified event in time.
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eed7f3508190995dcd39586ed614 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd6736c81909a6ca549f77b4345 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.