Triple
T14142300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portugal national rugby union team |
E350456
|
entity |
| Predicate | code |
P1537
|
FINISHED |
| Object | POR |
E149297
|
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: POR | Statement: [Portugal national rugby union team, code, POR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: POR Context triple: [Portugal national rugby union team, code, POR]
-
A.
POR
chosen
POR is the three-letter FIFA country code used to represent the Portugal national football team in international competitions and rankings.
-
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.
PAR
PAR is the standard abbreviation used for the Parramatta Eels, a professional rugby league club based in Sydney, Australia.
-
D.
PO
PO is the vehicle registration code used on license plates for the city of Požarevac in Serbia.
-
E.
PO
PO is a UK postcode area covering Portsmouth and surrounding parts of Hampshire and West Sussex.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de611ed3508190add37baa30d1d134 |
completed | April 14, 2026, 3:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcdf18e3d08190b287e2da192d05eb |
completed | May 7, 2026, 6:51 p.m. |
Created at: April 10, 2026, 12:48 a.m.