Triple
T28455366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wadō |
E716695
|
entity |
| Predicate | modernLocationOfDiscoverySite |
P3985
|
FINISHED |
| Object | Saitama Prefecture |
—
|
NE NERFINISHED |
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: Saitama Prefecture | Statement: [Wadō, modernLocationOfDiscoverySite, Saitama Prefecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernLocationOfDiscoverySite Context triple: [Wadō, modernLocationOfDiscoverySite, Saitama Prefecture]
-
A.
wasDiscoveredAt
chosen
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
B.
locatedAtTimeOfDiscovery
Indicates the place where something was situated at the moment it was first discovered.
-
C.
explorationSiteOf
Indicates that a location or site is the place where a particular exploration activity, mission, or project is conducted or associated.
-
D.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
-
E.
discoveredAsFossilSite
Indicates that a location was identified and recognized as a site containing fossils.
- 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_69efd6b76f8c8190a7ba908aca280942 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 28, 2026, 1:54 a.m.