Triple
T37069588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bingo Province |
E917537
|
entity |
| Predicate | hasDomainCenter |
P156819
|
FINISHED |
| Object | Fukuyama Castle |
—
|
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: Fukuyama Castle | Statement: [Bingo Province, hasDomainCenter, Fukuyama Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDomainCenter Context triple: [Bingo Province, hasDomainCenter, Fukuyama Castle]
-
A.
laterDomainCenter
Indicates that one domain center occurs at a later time or stage than another domain center within a given context.
-
B.
hasRAndDCenterIn
Indicates that an entity maintains a research and development (R&D) center located in a specified place.
-
C.
hasCentralSite
chosen
Indicates that an entity possesses or is associated with a primary or main site that serves as its central location or hub.
-
D.
domainCenter
Indicates that something is located at or serves as the central point or core area of a specified domain or region.
-
E.
hasCentralAdministrationIn
Indicates that an organization or entity maintains its primary central administrative authority or headquarters in a specified location.
- 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_69f76e9771e08190a690834e3cd20654 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:14 p.m.