Triple
T24030695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Fréjus-Toulon |
E595095
|
entity |
| Predicate | hasHistoricSeeCity |
P143563
|
FINISHED |
| Object | Fréjus |
—
|
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: Fréjus | Statement: [Diocese of Fréjus-Toulon, hasHistoricSeeCity, Fréjus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricSeeCity Context triple: [Diocese of Fréjus-Toulon, hasHistoricSeeCity, Fréjus]
-
A.
hasHistoricCity
Indicates that an entity possesses, contains, or is associated with a city recognized for its historical significance.
-
B.
hasSeeCity
Indicates that an entity has visited or observed a particular city.
-
C.
hasHistoricalSee
chosen
Indicates that one entity historically served as the episcopal see or central seat of authority for another entity, typically a diocese or bishopric.
-
D.
hasMetropolitanSeeCity
Indicates that an ecclesiastical jurisdiction is associated with, or headquartered in, a particular metropolitan (principal) city.
-
E.
hasTourHistory
Indicates that an entity has a record of past tours or tour-related activities.
- 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_69e288bf45f08190a1b6ed8cd0b9e86b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d76fbedc8190a2f936729cb69993 |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:55 p.m.