Triple
T11256237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 春の叙勲 |
E266444
|
entity |
| Predicate | 選考基準 |
P136
|
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: [春の叙勲, 選考基準, 功績の内容・期間・影響などを総合的に勘案する基準]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 選考基準 Context triple: [春の叙勲, 選考基準, 功績の内容・期間・影響などを総合的に勘案する基準]
-
A.
recruitmentBasis
Indicates the criteria, grounds, or conditions on which an entity is recruited or selected for a role or position.
-
B.
selectionCriteria
chosen
Indicates the conditions or rules used to choose certain entities from a larger set.
-
C.
admissionsBasedOn
Indicates that acceptance or entry decisions are determined according to specified criteria, factors, or conditions.
-
D.
evaluationCriteriaInclude
Indicates that certain criteria are part of, or explicitly included in, the set of standards used to evaluate something.
-
E.
evaluationBasis
Indicates the criteria, standards, or reference framework used to judge, assess, or measure something in an evaluation process.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e935b85c819085e1abf2dd4099c5 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d78793c00481908a3f764b610b77a4 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.