Triple
T25580383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peking Plan |
E641223
|
entity |
| Predicate | preparationDate |
P6878
|
FINISHED |
| Object | 1939-08 |
—
|
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: 1939-08 | Statement: [Peking Plan, preparationDate, 1939-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preparationDate Context triple: [Peking Plan, preparationDate, 1939-08]
-
A.
preparationPeriod
Indicates the time span allocated before an event or action during which necessary preparations are made.
-
B.
preparationBy
Indicates that one entity is created, assembled, or made ready through the actions or processes performed by another entity.
-
C.
preparationBegan
Indicates that the initial actions or processes required for something to be carried out or occur have started.
-
D.
preDates
Indicates that one entity existed, occurred, or was established earlier in time than another entity.
-
E.
dateOf
chosen
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f93364308190bcffdb00ee0ec6c7 |
completed | May 2, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69f4684442248190afe7677e56363e7f |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 4:11 p.m.