Triple
T7801502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krishna district |
E180442
|
entity |
| Predicate | hasVehicleRegistrationCode |
P1173
|
FINISHED |
| Object | AP |
E102106
|
NE 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: AP | Statement: [Krishna district, hasVehicleRegistrationCode, AP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AP Context triple: [Krishna district, hasVehicleRegistrationCode, AP]
-
A.
AP
AP is the standard abbreviation for the Pacific Alliance, a Latin American trade bloc focused on economic integration and free movement of goods, services, capital, and people among its member countries.
-
B.
AP
AP is a U.S.-based college-level program and exam system for high school students that can earn them advanced placement or credit at many universities.
-
C.
AP
AP is the vehicle registration code used on license plates for vehicles registered in the Argolis regional unit of Greece.
-
D.
AP
AP is the official two-letter postal abbreviation for the Brazilian state of Amapá.
-
E.
AP
chosen
AP is the official vehicle registration code for the Indian state of Andhra Pradesh.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca827e50cc8190a92a733577184938 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cae988bc2081909870bae1c2e9c238 |
completed | March 30, 2026, 9:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb142ba7788190a352a27cd57d1fdc |
completed | March 31, 2026, 12:24 a.m. |
Created at: March 30, 2026, 4:33 p.m.