Triple
T3264895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rennes |
E68501
|
entity |
| Predicate | populationRankInBrittany |
P25930
|
FINISHED |
| Object | largest city in Brittany |
—
|
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: largest city in Brittany | Statement: [Rennes, populationRankInBrittany, largest city in Brittany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationRankInBrittany Context triple: [Rennes, populationRankInBrittany, largest city in Brittany]
-
A.
populationRankInFrance
Indicates the relative position of an entity in an ordered list based on its population size within France.
-
B.
hasPopulationRankInDepartment
Indicates the relative position of an entity’s population size compared to other entities within the same department.
-
C.
hasPopulationRankInRegion
chosen
Indicates that an entity has a specific population-based rank or position within a defined geographic region.
-
D.
strengthFrance
Indicates a relationship where a level, measure, or attribute of strength is associated specifically with France.
-
E.
populationRank
Indicates the relative position of an entity in an ordered list based on the size of its population.
- 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_69ad8590444081909e8107a8aeef3a23 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adafcb2da08190a7f4fefdfe6d0098 |
completed | March 8, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69ada41d7eac8190ada4bf5f793d5c49 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.