Triple
T37261428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messapic language |
E924266
|
entity |
| Predicate | mainCorpusType |
P32641
|
FINISHED |
| Object | funerary inscriptions |
—
|
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: funerary inscriptions | Statement: [Messapic language, mainCorpusType, funerary inscriptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCorpusType Context triple: [Messapic language, mainCorpusType, funerary inscriptions]
-
A.
primaryCorpusType
chosen
Indicates the main or dominant type or category of corpus associated with an entity.
-
B.
corpus
Indicates that an entity is a collection or body of texts, documents, or linguistic data used as a unified set for analysis or reference.
-
C.
initialCorpus
Indicates that something serves as the original or starting collection of texts, data, or documents from which further processing, analysis, or derivation occurs.
-
D.
hasCorpusType
Indicates the type or category of corpus associated with an entity (e.g., text, speech, multimodal).
-
E.
hasPartOfCorpus
Indicates that one entity constitutes a component or segment of the overall corpus associated with another entity.
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: May 3, 2026, 4:15 p.m.