Triple
T25580365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peking Plan |
E641223
|
entity |
| Predicate | dateOfArrival |
P32352
|
FINISHED |
| Object | 1939-09-01 |
—
|
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-09-01 | Statement: [Peking Plan, dateOfArrival, 1939-09-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfArrival Context triple: [Peking Plan, dateOfArrival, 1939-09-01]
-
A.
deliveryDate
Indicates the specific date on which a product, service, or item is scheduled or expected to be delivered.
-
B.
subsequentArrivalDate
Indicates that one entity’s arrival date occurs after the arrival date of another related entity.
-
C.
arrivalByShip
Indicates that an entity reaches a destination specifically by traveling on a ship.
-
D.
estimatedArrivalInAustralia
Indicates the expected date and/or time when an entity is predicted to arrive in Australia.
-
E.
arrivalDatePlanned
chosen
Indicates the date on which an arrival is scheduled or expected to occur according to a plan.
- 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_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 4:11 p.m.