Triple
T27004750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toritsugi mediator |
E680210
|
entity |
| Predicate | termWrittenAs |
P95562
|
FINISHED |
| Object | 取次 |
—
|
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: 取次 | Statement: [Toritsugi mediator, termWrittenAs, 取次]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termWrittenAs Context triple: [Toritsugi mediator, termWrittenAs, 取次]
-
A.
termInCitation
Indicates that a specific term appears within, or is referenced by, a particular citation.
-
B.
writtenForm
Indicates that one entity is the textual or orthographic representation (spelling or written version) of another entity.
-
C.
isWrittenAs
chosen
Indicates that one entity is represented or expressed in written form as another entity (such as a specific spelling, notation, or symbol).
-
D.
nameWrittenIn
Indicates that an entity’s name is written or recorded using a specified language, script, or writing system.
-
E.
laterWrittenDownAs
Indicates that something was recorded or documented in written form at a subsequent time after its original occurrence or expression.
- 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621d139f081909f9ca04e04095dba |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 7 a.m.