Triple
T13753508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lycian League |
E330414
|
entity |
| Predicate | hasNumberOfVotesForLargestCities |
P110838
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Lycian League, hasNumberOfVotesForLargestCities, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfVotesForLargestCities Context triple: [Lycian League, hasNumberOfVotesForLargestCities, 3]
-
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.
hasHighestCity
Indicates that one entity possesses or contains the city with the greatest value according to some ranking criterion (e.g., highest population, elevation, or status) among a set of cities.
-
C.
hasCityRank
Indicates that a city holds a particular rank or position within a defined ordering or hierarchy (such as size, importance, or administrative level).
-
D.
largestCity
Indicates that one city is the most populous or significant urban center within a specified region or entity.
-
E.
numberOfVoters
Indicates the total count of individuals who participated in a particular vote or election.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0215cfa08190aaed8b089aff217b |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59db0148190bcaf9646403ca64f |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 10:09 p.m.