Triple
T29546294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Boeo |
E749637
|
entity |
| Predicate | modernCityAtSite |
P180623
|
FINISHED |
| Object | Marsala |
—
|
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: Marsala | Statement: [Cape Boeo, modernCityAtSite, Marsala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernCityAtSite Context triple: [Cape Boeo, modernCityAtSite, Marsala]
-
A.
modernCityOnSite
chosen
Indicates that a modern city is located on the same site as, or directly overlies, an earlier settlement or place.
-
B.
modernCityBuiltAround
Indicates that a contemporary or recently developed city has been constructed encircling or surrounding a particular central feature, structure, or area.
-
C.
modernCityIs
Indicates that something possesses the characteristics or status of being a modern city.
-
D.
modernSiteOfCapital
Indicates that the subject location is the present-day site where the capital of the object political entity is situated.
-
E.
modernCityServed
Indicates that a modern city receives services, support, or functions (such as transportation, utilities, or administration) from a specified provider or infrastructure.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 28, 2026, 5:08 p.m.