Triple
T20320027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Textus Receptus |
E492184
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | TR |
—
|
NE NERFINISHED |
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: TR | Statement: [Textus Receptus, hasAbbreviation, TR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TR Context triple: [Textus Receptus, hasAbbreviation, TR]
-
A.
TR
TR is the two-letter ISO 3166-1 alpha-2 country code assigned to Turkey for international standardization and referencing.
-
B.
TR
TR is the postcode area covering Truro and much of Cornwall in southwest England.
-
C.
TR
chosen
TR is the common abbreviation for the Textus Receptus, a historically influential printed Greek New Testament text that underlies many early Protestant Bible translations.
-
D.
TR
TR is the IATA airport code for Singapore-based low-cost airline Scoot.
-
E.
tr
tr is a GNU Core Utilities command-line program used to translate, squeeze, or delete characters from standard input and write the result to standard output.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778abd14819098a01fd32217fdde |
completed | April 20, 2026, 6:59 p.m. |
Created at: April 16, 2026, 11:20 a.m.