Triple
T6681452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tetã Paraguái |
E151990
|
entity |
| Predicate | ISO3166-1Alpha3 |
P189
|
FINISHED |
| Object | PRY |
E151992
|
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: PRY | Statement: [Tetã Paraguái, ISO3166-1Alpha3, PRY]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PRY Context triple: [Tetã Paraguái, ISO3166-1Alpha3, PRY]
-
A.
PRY
chosen
PRY is the three-letter ISO 3166-1 alpha-3 country code assigned to Paraguay.
-
B.
Prysm
Prysm is a widely used Ethereum consensus client implementation written in Go that helps manage validators and secure the network under proof-of-stake.
-
C.
Pyr
Pyr is a science fiction and fantasy publishing imprint known for releasing speculative fiction titles under the Prometheus Books umbrella.
-
D.
Perly
Perly is a Swiss village in the canton of Geneva, situated near the French border and forming part of the commune of Perly-Certoux.
-
E.
Repyt
Repyt is an ancient Egyptian lioness goddess primarily worshipped at Akhmim, associated with protection and sometimes linked to solar and warlike aspects.
- 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_69c687f9977c819097e7f5ada4fe522e |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6b11f945481908e1a9f0839c35b5b |
completed | March 27, 2026, 4:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6f7ac6714819081966dea66b590c1 |
completed | March 27, 2026, 9:33 p.m. |
Created at: March 27, 2026, 2:04 p.m.