Triple
T15392416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 長堀鶴見緑地線 |
E368079
|
entity |
| Predicate | 開業目的 |
P25761
|
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.
purposeOfIncorporation
Indicates that an entity was incorporated with the specific goal, function, or intended activity described by another entity or statement.
-
B.
opensShopTo
Indicates that one entity makes a shop accessible or available for another entity, typically by starting or unlocking its operation for them.
-
C.
aimedToEstablish
Indicates an intention or effort directed toward creating, founding, or setting up something.
-
D.
intendedOpeningUse
Indicates that an opening (such as a door, window, or passage) is designed or meant to be used for a particular purpose or function.
-
E.
openingMotive
chosen
Indicates the initial reason, trigger, or intent that prompts an action or event to begin.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e7838b48190862b43c6c8620692 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.