Triple
T9346120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukuyama |
E224894
|
entity |
| Predicate | isCommercialCity |
P13740
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Fukuyama, isCommercialCity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommercialCity Context triple: [Fukuyama, isCommercialCity, true]
-
A.
hasMajorCommercialCentre
Indicates that a place contains or hosts a primary hub of significant commercial or business activity.
-
B.
isMajorCityIn
Indicates that a city is a primary or significant urban center located within a specified larger region or country.
-
C.
isCityOf
Indicates that one entity is a city that belongs to, is located within, or is administratively part of another entity (such as a country, state, or region).
-
D.
isGlobalCity
Indicates that a city holds significant worldwide influence in areas such as economics, culture, politics, or connectivity, making it an important node in the global system.
-
E.
isEconomicCenter
chosen
Indicates that an entity functions as a primary hub for economic activity, such as trade, finance, or industry, within a region or system.
- 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_69ca842993248190a79ab06968994b86 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4f0e2ccc8190a68f1c96c0886660 |
completed | April 1, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69cc7a66aef08190b8d668cff5b04f5f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:41 p.m.