Triple
T23343562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Short-term Economic Survey of Enterprises in Japan |
E591796
|
entity |
| Predicate | responseUnit |
P151947
|
FINISHED |
| Object | enterprise |
—
|
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: enterprise | Statement: [Short-term Economic Survey of Enterprises in Japan, responseUnit, enterprise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responseUnit Context triple: [Short-term Economic Survey of Enterprises in Japan, responseUnit, enterprise]
-
A.
responseField
Indicates that a particular piece of information is included as part of a response or output structure.
-
B.
responseSetting
Indicates the contextual conditions or configuration under which a response is produced or intended to be used.
-
C.
responseTool
Indicates a tool, method, or mechanism used to produce, deliver, or manage a response in a given context.
-
D.
responseFrom
Indicates that one entity is the originator or source of a response directed to another entity or request.
-
E.
responseExample
Indicates that one entity serves as an illustrative or sample response corresponding to another entity (such as a prompt, question, or situation).
- F. None of above. chosen
Provenance (4 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1983431f08190b0078728d44872a8 |
completed | April 29, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:18 p.m.