Triple
T33116859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Department of the Seine |
E847480
|
entity |
| Predicate | hadLargestCity |
P235
|
FINISHED |
| Object | Paris |
—
|
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: Paris | Statement: [Department of the Seine, hadLargestCity, Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadLargestCity Context triple: [Department of the Seine, hadLargestCity, Paris]
-
A.
isLargestCityIn
Indicates that one city has the greatest population or size compared to all other cities within a specified region or administrative area.
-
B.
largestCity
chosen
Indicates that one city is the most populous or significant urban center within a specified region or entity.
-
C.
areLargestCitiesOf
Indicates that the subject entities are the largest cities within the regions or countries specified by the object entities.
-
D.
isLargestTownOn
Indicates that one town is the largest (by size, population, or another defined measure) among all towns located on a specified geographic feature or area.
-
E.
formerLargestCity
Indicates that a city was previously the largest city (by population or size) within a given region or context, but no longer holds that status.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6ee6e2081909c55bf6b31356d61 |
completed | May 3, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.