Triple
T21439612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 農学部 |
E528902
|
entity |
| Predicate | 主な進路 |
P143950
|
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.
majorRouteTo
Indicates that one location serves as a primary or significant route or pathway leading to another location.
-
B.
主なレジャー
Indicates the primary or most common leisure activity associated with an entity.
-
C.
educationalPathway
Indicates the sequence or structure of educational steps, programs, or qualifications that connect one stage of learning or training to another.
-
D.
primaryRoute
Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
-
E.
developmentPathwayFor
Indicates that one entity serves as a route, mechanism, or process through which the development or progression of another entity occurs.
- 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b6feb2e48190ba5649f16a8bbbda |
completed | April 22, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 6:05 p.m.