Triple
T13753510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lycian League |
E330414
|
entity |
| Predicate | hasNumberOfVotesForSmallCities |
P73372
|
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: [Lycian League, hasNumberOfVotesForSmallCities, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfVotesForSmallCities Context triple: [Lycian League, hasNumberOfVotesForSmallCities, 1]
-
A.
isSmallCity
Indicates that a city has a relatively small population size or limited geographic/urban extent compared to typical cities.
-
B.
isSmallDistrict
Indicates that a district is classified as small, typically based on its limited size, population, or administrative scope.
-
C.
electoralCity
Indicates that a city serves as the designated location where electoral activities (such as voting or election administration) for a given entity take place.
-
D.
numberOfVoters
Indicates the total count of individuals who participated in a particular vote or election.
-
E.
hasNumberOfVotesAllocatedBy
chosen
Indicates that a specific number of votes has been assigned or allocated to an entity by another entity.
- 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_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. |
Created at: April 9, 2026, 10:09 p.m.