Triple
T10827905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenStreetMap |
E255539
|
entity |
| Predicate | editingMethod |
P87783
|
FINISHED |
| Object | crowdsourcing |
—
|
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: crowdsourcing | Statement: [OpenStreetMap, editingMethod, crowdsourcing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editingMethod Context triple: [OpenStreetMap, editingMethod, crowdsourcing]
-
A.
editingIs
Indicates that one entity is performing or undergoing the process of editing another entity.
-
B.
editingMode
Indicates that an entity is currently in, or associated with, a state where its content or properties can be modified or edited.
-
C.
editingBody
Indicates that one entity is serving as the editorial body responsible for reviewing, modifying, or overseeing the content or work of another entity.
-
D.
editingProcess
chosen
Indicates the process by which content is reviewed, modified, and refined to improve clarity, accuracy, or quality.
-
E.
coEditor
Indicates that two or more entities share responsibility for editing the same work or publication.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d734d2b9f88190b79a7b168d7836c8 |
completed | April 9, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.