Triple
T9300960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarleton |
E223758
|
entity |
| Predicate | postcodeArea |
P920
|
FINISHED |
| Object | PR |
E662
|
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: PR | Statement: [Tarleton, postcodeArea, PR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PR Context triple: [Tarleton, postcodeArea, PR]
-
A.
PR
chosen
PR is the two-letter postal abbreviation commonly used to refer to Puerto Rico, a Caribbean island and unincorporated territory of the United States.
-
B.
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.
-
C.
PRO
PRO is the Professional Referee Organization that manages and develops professional soccer match officials in the United States and Canada.
-
D.
Prem
Prem is an Indian given name commonly used for males, derived from Sanskrit and meaning "love" or "affection."
-
E.
Prem
Prem is a small rural municipality in the district of Weilheim-Schongau in Bavaria, Germany.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd08d1d954819098be177addafa406 |
completed | April 1, 2026, noon |
| NED1 | Entity disambiguation (via context triple) | batch_69d0b26302608190a59f3ed0694ce6d9 |
completed | April 4, 2026, 6:40 a.m. |
Created at: March 30, 2026, 7:36 p.m.