Triple
T29930453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lionel Loueke |
E760199
|
entity |
| Predicate | hasLinguisticAbility |
P29822
|
FINISHED |
| Object | French |
—
|
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: French | Statement: [Lionel Loueke, hasLinguisticAbility, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLinguisticAbility Context triple: [Lionel Loueke, hasLinguisticAbility, French]
-
A.
languageCapacity
chosen
Indicates the extent to which an entity is able to understand, produce, or otherwise use language.
-
B.
hasLinguist
Indicates that an entity is associated with or possesses a linguist, typically as a member, employee, collaborator, or resource.
-
C.
hasLinguisticFeature
Indicates that an entity possesses a particular linguistic property, trait, or characteristic.
-
D.
hasLinguisticDocumentation
Indicates that there exists recorded linguistic information or documentation about the language or linguistic properties of the subject.
-
E.
hasLinguisticPresenceOf
Indicates that something exhibits, contains, or demonstrates the presence of a particular linguistic element, feature, or expression.
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: April 29, 2026, 6:17 p.m.