Triple
T23638953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L’nu |
E583831
|
entity |
| Predicate | relatedFormMeaning |
P21674
|
FINISHED |
| Object | the people (plural) in Mi’kmaq |
—
|
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: the people (plural) in Mi’kmaq | Statement: [L’nu, relatedFormMeaning, the people (plural) in Mi’kmaq]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedFormMeaning Context triple: [L’nu, relatedFormMeaning, the people (plural) in Mi’kmaq]
-
A.
relatedForm
chosen
Indicates that one entity is an alternative or variant form of another, such as a different spelling, inflection, or closely related lexical form.
-
B.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
-
C.
centralFormulaMeaning
Indicates that one formula or expression represents the primary or core meaning within a larger logical, mathematical, or semantic structure.
-
D.
semanticRootMeaning
Indicates the fundamental or core meaning that underlies a word, phrase, or expression in a semantic structure.
-
E.
meaningInArabicRelatedForm
Indicates that one entity expresses the meaning of another entity in Arabic through a related or derived linguistic form.
- 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_69e248fe1c2c8190ac914d2442ff3d26 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b27fc22c8190abda7398b9fb928c |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:48 p.m.