Triple
T27992925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matteo Ricci |
E706927
|
entity |
| Predicate | arrivedInBeijing |
P165111
|
FINISHED |
| Object | 1601 |
—
|
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: 1601 | Statement: [Matteo Ricci, arrivedInBeijing, 1601]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arrivedInBeijing Context triple: [Matteo Ricci, arrivedInBeijing, 1601]
-
A.
arrivedInMainlandChina
Indicates that an entity has reached and entered the territory of mainland China from elsewhere.
-
B.
arrivedInMacau
Indicates that an entity has reached or come to the location of Macau.
-
C.
returnedToChina
Indicates that an entity went back to China after having been away.
-
D.
laterSettledIn
Indicates that one entity moved to and established residence in a place or community at a subsequent time, after an earlier location or phase in their life.
-
E.
distanceFromBeijing_km
Indicates the physical distance, measured in kilometers, between a given place or object and Beijing.
- F. None of above. chosen
Provenance (4 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 27, 2026, 7:51 p.m.