Triple
T37188287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyooka-shi |
E921378
|
entity |
| Predicate | hasWildlifeConservationArea |
P92447
|
FINISHED |
| Object | Oriental white stork habitat |
—
|
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: Oriental white stork habitat | Statement: [Toyooka-shi, hasWildlifeConservationArea, Oriental white stork habitat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWildlifeConservationArea Context triple: [Toyooka-shi, hasWildlifeConservationArea, Oriental white stork habitat]
-
A.
hasWildernessArea
Indicates that one entity possesses, contains, or is associated with a designated wilderness area.
-
B.
hasWildlifeRegion
Indicates that an entity is associated with or located within a designated wildlife region or habitat area.
-
C.
containsWildernessArea
Indicates that one entity geographically includes or encompasses a designated wilderness area within its boundaries.
-
D.
hasWildlifeHabitats
chosen
Indicates that an entity contains or supports natural environments where wildlife species live, feed, or reproduce.
-
E.
hasWildlifeSite
Indicates that a location or entity possesses, contains, or is designated as a wildlife site.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.