Triple
T27670012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Verdy 1969 |
E697632
|
entity |
| Predicate | laterShortenedName |
P99167
|
FINISHED |
| Object | Tokyo Verdy |
—
|
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: Tokyo Verdy | Statement: [Tokyo Verdy 1969, laterShortenedName, Tokyo Verdy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterShortenedName Context triple: [Tokyo Verdy 1969, laterShortenedName, Tokyo Verdy]
-
A.
nameShort
Indicates that an entity has a shortened or abbreviated version of its full name.
-
B.
commonShortNameFor
chosen
Indicates that one entity is a commonly used short or abbreviated name for another entity.
-
C.
termShortenedBy
Indicates that one term is a shortened, abbreviated, or truncated form derived from another term.
-
D.
isShortName
Indicates that one name is an abbreviated or shorter form of another name.
-
E.
bearerShortName
Indicates that an entity serves as the short or abbreviated name used to identify the bearer in the context of a relationship or action.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: April 27, 2026, 2:40 p.m.