Triple
T6430608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tankan survey |
E128167
|
entity |
| Predicate | respondentType |
P13832
|
FINISHED |
| Object | corporations |
—
|
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: corporations | Statement: [Tankan survey, respondentType, corporations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: respondentType Context triple: [Tankan survey, respondentType, corporations]
-
A.
respondentStatus
Indicates the current role, condition, or state of a respondent in relation to a survey, inquiry, or legal/administrative process.
-
B.
respondentBusiness
chosen
Indicates that a business entity is the one providing answers or participating as the responding party in a survey, form, or legal/administrative process.
-
C.
respondentPosition
Indicates the role, title, or job position held by a respondent in the context of a survey, study, or inquiry.
-
D.
respondentRequirement
Indicates that a particular condition, qualification, or obligation must be met by the respondent in order to participate in or complete the referenced activity or process.
-
E.
namedPartyType
Indicates the specific role or category that a referenced party holds within a given context or relationship.
- 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.