Triple
T32136868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanaka Tatsuya |
E820788
|
entity |
| Predicate | hasRepresentationOnPlatform |
P203739
|
FINISHED |
| Object |
E5329
|
NE 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: Instagram | Statement: [Tanaka Tatsuya, hasRepresentationOnPlatform, Instagram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRepresentationOnPlatform Context triple: [Tanaka Tatsuya, hasRepresentationOnPlatform, Instagram]
-
A.
occursOnPlatform
Indicates that an event, action, or process takes place or is carried out on a specified platform.
-
B.
hasPlatformOn
Indicates that one entity is physically supported by or situated on the surface or structure of another entity.
-
C.
usedOnPlatformType
Indicates that something is utilized or operates on a specific type of platform.
-
D.
hasPrimaryPlatform
Indicates that one entity is designated as the main or principal platform associated with another entity.
-
E.
hasPlatformType
Indicates that an entity is associated with or characterized by a specific type or category of platform.
- F. None of above. chosen
Provenance (5 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01d9ca07b88190b4ad70b6336447b6 |
completed | May 11, 2026, 1:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f01371bd88190a447bdea6f290210 |
completed | June 14, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_6a01d807c3048190b79f0b6b933dd3b7 |
completed | May 11, 2026, 1:22 p.m. |
| PDg | Predicate description generation | batch_6a01d9c926508190936f05ce4a19c20d |
completed | May 11, 2026, 1:29 p.m. |
Created at: May 1, 2026, 12:30 a.m.