Triple
T20774855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mo Folchart |
E511328
|
entity |
| Predicate | languageOfAbility |
P741
|
FINISHED |
| Object | reading in his own language |
—
|
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: reading in his own language | Statement: [Mo Folchart, languageOfAbility, reading in his own language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfAbility Context triple: [Mo Folchart, languageOfAbility, reading in his own language]
-
A.
languagesSpoken
chosen
Indicates that an entity is able to communicate using one or more specified languages.
-
B.
languageGroupSpoken
Indicates that a particular language group is spoken or used for communication by an entity.
-
C.
languageOfExpression
Indicates that a particular language is used as the medium or form in which an expression (such as a text, utterance, or work) is realized.
-
D.
eligibleLanguage
Indicates that a particular language satisfies the required conditions to be considered valid or allowed in a given context.
-
E.
languageCapacity
Indicates the extent to which an entity is able to understand, produce, or otherwise use 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c26a39bc81909ca5d102056d8586 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:37 p.m.