Triple
T27992923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matteo Ricci |
E706927
|
entity |
| Predicate | laterBasedInNanchang |
P64727
|
FINISHED |
| Object | 1595 |
—
|
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: 1595 | Statement: [Matteo Ricci, laterBasedInNanchang, 1595]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterBasedInNanchang Context triple: [Matteo Ricci, laterBasedInNanchang, 1595]
-
A.
basedInCity
Indicates that an entity has its primary location, headquarters, or main operations situated in a specified city.
-
B.
basedInLater
chosen
Indicates that an entity is located or headquartered in a place during a later time period or phase, relative to some earlier location or state.
-
C.
basedInUntil
Indicates that an entity was based or located in a particular place up to a specified end time or date, after which this association ceased.
-
D.
isTypicallyBasedIn
Indicates that one entity is most commonly located, headquartered, or primarily operates within the context or place specified by another entity.
-
E.
laterLivedIn
Indicates that one entity resided in a particular place during a later period of its life, after an earlier residence elsewhere.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: April 27, 2026, 7:51 p.m.