Triple
T35446979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 東洋のルソー |
E1024513
|
entity |
| Predicate | refersToPersonPlaceOfActivity |
P137759
|
FINISHED |
| Object | 東京 |
—
|
NE NERFINISHED |
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: 東京 | Statement: [東洋のルソー, refersToPersonPlaceOfActivity, 東京]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToPersonPlaceOfActivity Context triple: [東洋のルソー, refersToPersonPlaceOfActivity, 東京]
-
A.
refersToPerson
Indicates that one entity is making reference to, mentioning, or pointing specifically to a particular person.
-
B.
personAssociatedPlace
Indicates that a person has a notable connection or association with a particular place, such as residence, origin, work, or frequent presence.
-
C.
possiblePlaceOfActivity
chosen
Indicates that a location is a plausible or candidate site where the referenced entity may carry out or have carried out an activity.
-
D.
placeOfBusinessActivity
Indicates the type or nature of business activity that is conducted at a particular place or location.
-
E.
appellationOfActivity
Indicates that a given name, label, or title is used to designate a particular activity.
- 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: May 3, 2026, 4:04 p.m.