Triple
T4832156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wikipedia puzzle globe |
E107968
|
entity |
| Predicate | appliesToProject |
P1129
|
FINISHED |
| Object | all language editions of Wikipedia |
—
|
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: all language editions of Wikipedia | Statement: [Wikipedia puzzle globe, appliesToProject, all language editions of Wikipedia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToProject Context triple: [Wikipedia puzzle globe, appliesToProject, all language editions of Wikipedia]
-
A.
appliesTo
chosen
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
B.
affectedByProject
Indicates that an entity experiences an impact, change, or influence as a result of a specific project.
-
C.
hasProjectIn
Indicates that an entity is involved with or associated with a project that takes place within a specified location or context.
-
D.
appliesToFeature
Indicates that something (such as a rule, constraint, or configuration) is relevant to, or governs, a specific feature.
-
E.
usedInProject
Indicates that something (such as a resource, tool, or component) is employed or utilized within a particular project.
- 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.