Triple
T5414813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suffetes |
E121103
|
entity |
| Predicate | originalLanguageOfTerm |
P28203
|
FINISHED |
| Object | Punic |
—
|
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: Punic | Statement: [Suffetes, originalLanguageOfTerm, Punic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalLanguageOfTerm Context triple: [Suffetes, originalLanguageOfTerm, Punic]
-
A.
originalLanguagePhrase
Indicates that one phrase is the original-language version from which another phrase (typically a translation or adaptation) is derived.
-
B.
originalLanguageCountry
Indicates the country where a work’s original language is primarily spoken or officially used.
-
C.
originalLanguageContext
Indicates the language in which something was first created or expressed, providing the original linguistic context for its content or meaning.
-
D.
originalTextLanguage
Indicates the language in which a text was originally written or created before any translation or adaptation.
-
E.
originalNameLanguage
chosen
Indicates that the specified language is the language in which an entity’s original or primary name was expressed.
- 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87bcace08190932fe85e4b4aeffc |
completed | March 20, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69bd8469f5e48190bbe5c8bdfe8925ea |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.