Triple
T3499806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sorisdale |
E73937
|
entity |
| Predicate | hasPostcodeArea |
P920
|
FINISHED |
| Object | PA |
E136742
|
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: PA | Statement: [Sorisdale, hasPostcodeArea, PA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PA Context triple: [Sorisdale, hasPostcodeArea, PA]
-
A.
PA
PA is the standard two-letter U.S. Postal Service abbreviation for the state of Pennsylvania.
-
B.
PA
chosen
PA is the postcode area in western Scotland that covers Paisley and parts of the surrounding Greater Glasgow region.
-
C.
PA
The Palestinian Authority is an interim self-governing body established to administer parts of the West Bank and Gaza Strip as part of the Israeli-Palestinian peace process.
-
D.
PAL
PAL is the ICAO airline designator for Philippine Airlines, the flag carrier of the Philippines.
-
E.
PAR
PAR is the IATA city code representing the collective airport system serving Paris, France, including major airports such as Charles de Gaulle and Orly.
- 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_69ad85cdb6e48190a335d412b9194ed8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbd4eb308190b84e84261ceec229 |
completed | March 8, 2026, 6:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b373d2ef9c819087458a0ac02d4596 |
completed | March 13, 2026, 2:17 a.m. |
Created at: March 8, 2026, 3:18 p.m.