Triple
T9989984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moabite language |
E196860
|
entity |
| Predicate | primaryCorpusSize |
P18537
|
FINISHED |
| Object | very small |
—
|
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: very small | Statement: [Moabite language, primaryCorpusSize, very small]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCorpusSize Context triple: [Moabite language, primaryCorpusSize, very small]
-
A.
primaryCorpusType
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.
hasLimitedCorpus
chosen
Indicates that the associated entity possesses only a small or restricted set of available data, texts, or examples for use or analysis.
-
D.
hasPartOfCorpus
Indicates that one entity constitutes a component or segment of the overall corpus associated with another entity.
-
E.
traditionalPlacementInCorpus
Indicates the conventional or historically established position of a work or text within a larger corpus or collection.
- 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_69ca82f1678c819093d06320a05f16a4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdc79f3df08190ab3094ad1cd5490f |
completed | April 2, 2026, 1:34 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:50 p.m.