Triple
T33714059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maemo |
E863820
|
entity |
| Predicate | communityFork |
P178664
|
FINISHED |
| Object | Maemo Leste |
—
|
NE NERFINISHED |
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: Maemo Leste | Statement: [Maemo, communityFork, Maemo Leste]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communityFork Context triple: [Maemo, communityFork, Maemo Leste]
-
A.
communityAspect
Indicates that something pertains to, reflects, or influences the communal or social dimension of a group or community.
-
B.
community
Indicates a relationship where individuals or groups are connected by shared location, interests, or identity, forming a collective social unit.
-
C.
communitySpace
Indicates a relationship where a location or resource is designated for shared use, activities, or gatherings by members of a community.
-
D.
coreCommunity
Indicates that an entity belongs to the central or most essential group within a larger community.
-
E.
communityBoard
Indicates a relationship where an entity serves as or is associated with a local governing or advisory community board responsible for representing and addressing community interests.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f713bfdc148190a249a7874320bab8 |
completed | May 3, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f7135fa2988190a20a94cfe616d754 |
completed | May 3, 2026, 9:20 a.m. |
Created at: May 1, 2026, 1:44 a.m.