Triple
T34059964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Venoge |
E873467
|
entity |
| Predicate | creatorLanguageCommunity |
P199397
|
FINISHED |
| Object | Romand |
—
|
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: Romand | Statement: [La Venoge, creatorLanguageCommunity, Romand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creatorLanguageCommunity Context triple: [La Venoge, creatorLanguageCommunity, Romand]
-
A.
creatorLanguage
Indicates the language in which the creator produced or expressed the related work or content.
-
B.
programmingLanguageCommunity
Indicates a relationship where a group of people are collectively engaged with, support, and interact around a particular programming language.
-
C.
languageCreatedBy
Indicates that a particular language was created, designed, or originated by a specific person or group.
-
D.
coAuthorOfLanguage
Indicates that two or more entities jointly authored, designed, or created a particular language.
-
E.
languagesUsed
Indicates that one entity uses, employs, or is expressed in one or more languages associated with the other entity.
- F. None of above. chosen
Provenance (4 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69ff3705e424819090ad7423ceefa506 |
completed | May 9, 2026, 1:30 p.m. |
Created at: May 1, 2026, 1:52 a.m.