Triple
T30960980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goemai |
E788819
|
entity |
| Predicate | hasPrimaryDocumentationLanguage |
P83252
|
FINISHED |
| Object | English |
—
|
NE NERFINISHED |
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: English | Statement: [Goemai, hasPrimaryDocumentationLanguage, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryDocumentationLanguage Context triple: [Goemai, hasPrimaryDocumentationLanguage, English]
-
A.
hasPrimaryLanguage1
chosen
Indicates that an entity’s main or most commonly used language is the specified language.
-
B.
hasPrimaryVernacularLanguageFamily
Indicates that an entity’s main vernacular language belongs to a specified language family.
-
C.
hasPrimaryTraditionalLanguage
Indicates that one entity is the main or principal traditional language associated with another entity.
-
D.
isLanguageOf
Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
-
E.
hasPrimaryLanguageOfOperations
Indicates that an entity conducts its main activities or operations primarily using a specified language.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00233e2170819084bee0c8f74cc1a4 |
completed | May 10, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_6a0022943fd08190b73007f080d5971d |
completed | May 10, 2026, 6:15 a.m. |
Created at: April 29, 2026, 8:54 p.m.