Triple
T28631010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanian Wikipedia |
E724638
|
entity |
| Predicate | mobileAppSupport |
P166495
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Romanian Wikipedia, mobileAppSupport, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mobileAppSupport Context triple: [Romanian Wikipedia, mobileAppSupport, yes]
-
A.
developerSupport
Indicates that one entity provides technical assistance, resources, or guidance to help another entity develop, maintain, or improve software or related systems.
-
B.
digitalSupport
Indicates that one entity provides assistance, resources, or services to another through digital or online means.
-
C.
surfaceApplication
Indicates that a substance, treatment, or process is applied to the outer surface of an object or material.
-
D.
applicationModelSupport
Indicates that one entity provides support, compatibility, or services for another entity’s application model or application-level behavior.
-
E.
applicationTool
Indicates that one entity is a tool or instrument used to apply, operate, or carry out the function of another 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6622808b48190bbabcc75288ab031 |
completed | May 2, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f6617a7e7c81908cfac4a2250797ee |
completed | May 2, 2026, 8:41 p.m. |
Created at: April 28, 2026, 4:37 a.m.