Triple
T29504815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gentoo Wiki |
E748481
|
entity |
| Predicate | registrationPurpose |
P122245
|
FINISHED |
| Object | editing |
—
|
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: editing | Statement: [Gentoo Wiki, registrationPurpose, editing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registrationPurpose Context triple: [Gentoo Wiki, registrationPurpose, editing]
-
A.
accessPurpose
Indicates that one entity uses or accesses another entity specifically for a defined purpose or intended use.
-
B.
registrationFor
chosen
Indicates a relationship where one entity is enrolled, signed up, or formally recorded to participate in, use, or be associated with another entity (such as an event, service, or program).
-
C.
tagPurpose
Indicates the intended role, function, or use associated with a given tag in a particular context.
-
D.
servicePurpose
Indicates that one entity serves as the purpose, goal, or intended function for which another entity (typically a service) exists or is provided.
-
E.
purposeOfAddress
Indicates the reason or intended use for which a particular address is provided or utilized.
- 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 4:27 p.m.