Triple
T3555977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linz |
E75219
|
entity |
| Predicate | isLargestCityRankInAustria |
P50570
|
FINISHED |
| Object | third |
—
|
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: third | Statement: [Linz, isLargestCityRankInAustria, third]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLargestCityRankInAustria Context triple: [Linz, isLargestCityRankInAustria, third]
-
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.
isFourthLargestCityIn
Indicates that a city is the fourth most populous or significant city within a specified larger region or country.
-
C.
largestCantonByPopulation
Indicates that the subject is the canton with the highest population among a specified set or within a given region.
-
D.
AustrianDesignation
Indicates that an entity has an official designation, title, or status specifically within the Austrian context (e.g., by Austrian law, administration, or standards).
-
E.
largerCityInCountry
Indicates that one city is larger than another city within the same country.
- F. None of above. chosen
Provenance (4 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_69ad85d45090819086f34fb85d850a1e |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0569fbc81909b855b6990c1415b |
completed | March 8, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69adb83270ac819083967db0570167d2 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adba25c66c81909a05a97327828c41 |
completed | March 8, 2026, 6:04 p.m. |
Created at: March 8, 2026, 3:20 p.m.