Triple
T6430602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tankan survey |
E128167
|
entity |
| Predicate | publicationSchedule |
P47702
|
FINISHED |
| Object | early April |
—
|
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: early April | Statement: [Tankan survey, publicationSchedule, early April]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicationSchedule Context triple: [Tankan survey, publicationSchedule, early April]
-
A.
publicationScheduleChange
Indicates a change in the planned timing or frequency with which something is published or released.
-
B.
publicationFrequency
Indicates how often a publication or content is issued, released, or made available over a given period.
-
C.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
-
D.
publisherPlanned
chosen
Indicates that a publisher has scheduled or intends to release or distribute a particular work or item.
-
E.
publishesFor
Indicates that one entity issues, releases, or makes content publicly available on behalf of, or in service of, another entity.
- 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_69c00838de888190af2eec0b80495efa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0693b872c819082a7d0e257018831 |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f780b08190aa650b4d1fc51f21 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:44 p.m.