Triple
T29021242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italy and Africa |
E737455
|
entity |
| Predicate | includedKeyCity |
P41762
|
FINISHED |
| Object | Rome |
—
|
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: Rome | Statement: [Italy and Africa, includedKeyCity, Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedKeyCity Context triple: [Italy and Africa, includedKeyCity, Rome]
-
A.
notableCityIncluded
chosen
Indicates that a notable or significant city is contained within, or is part of, a larger geographic or administrative entity.
-
B.
mentionsCity
Indicates that one entity refers to or brings up a particular city in some form of communication or content.
-
C.
significantCityCovered
Indicates that a significant city lies within the geographic area or scope covered by something (such as a service, event, or phenomenon).
-
D.
majorCityAlong
Indicates that a major city is located along the course or path of a specified geographic feature, such as a river, road, or route.
-
E.
containsCapitalCity
Indicates that a geographic or political region includes within its boundaries the capital city associated with it.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ff691f5ae481908597ce245188d31c |
completed | May 9, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69ff67ceeeb081909fd00cad166c4b6a |
completed | May 9, 2026, 4:58 p.m. |
Created at: April 28, 2026, 9:49 a.m.