Triple
T15967074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legia Warsaw |
E387218
|
entity |
| Predicate | homeCityPopulationRankInPoland |
P25930
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Legia Warsaw, homeCityPopulationRankInPoland, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCityPopulationRankInPoland Context triple: [Legia Warsaw, homeCityPopulationRankInPoland, 1]
-
A.
rankByFrequencyInPoland
Indicates the relative ordering of entities based on how often they occur or appear in Poland.
-
B.
hasPopulationRank
Indicates the relative position of an entity in an ordered list based on the size of its population.
-
C.
regionalCapitalOfVoivodeship
Indicates that a location serves as the administrative capital of a specific voivodeship (province or region).
-
D.
hasPopulationRankInRegion
chosen
Indicates that an entity has a specific population-based rank or position within a defined geographic region.
-
E.
voivodeshipCapitalSince
Indicates that a location has served as the capital of a voivodeship (an administrative region) starting from a specified point in time.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.