Triple
T4577329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tranquebar |
E123168
|
entity |
| Predicate | languageHistory |
P30358
|
FINISHED |
| Object | site of early Tamil Bible translation |
—
|
LITERAL 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: site of early Tamil Bible translation | Statement: [Tranquebar, languageHistory, site of early Tamil Bible translation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageHistory Context triple: [Tranquebar, languageHistory, site of early Tamil Bible translation]
-
A.
historicalLanguage
Indicates that one language is a historical or earlier form/ancestor of another language.
-
B.
ethnicHistory
Indicates a relationship where one entity documents, describes, or is associated with the historical development, experiences, or heritage of an ethnic group.
-
C.
historicalLanguageFeature
Indicates that a language possesses a feature, trait, or characteristic that existed or was relevant in a past historical period.
-
D.
historicallySpoke
Indicates that an entity used a particular language as a spoken language during some period in the past.
-
E.
languageOfHistoricalRecord
chosen
Indicates the language in which a given historical record is written or recorded.
- F. None of above.
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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58e153908190ac8f578e03aecdfc |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.