Triple
T29408859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gentoo QA guidelines |
E745840
|
entity |
| Predicate | isDocumentedOn |
P28142
|
FINISHED |
| Object | Gentoo Wiki |
—
|
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: Gentoo Wiki | Statement: [Gentoo QA guidelines, isDocumentedOn, Gentoo Wiki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDocumentedOn Context triple: [Gentoo QA guidelines, isDocumentedOn, Gentoo Wiki]
-
A.
documentedUsing
Indicates that something is recorded, described, or specified by means of a particular document, tool, or documentation method.
-
B.
documentedFrom
Indicates that information about one entity is derived from, recorded in, or supported by another entity as its source of documentation.
-
C.
documentedThrough
Indicates that something is recorded, evidenced, or made known by means of a specific document or documentation process.
-
D.
hasDocumentationAt
chosen
Indicates that something is documented or described in a specific document, file, or location.
-
E.
isBetterDocumentedMemberOf
Indicates that one entity is a member of a group or set whose documentation quality is higher or more complete than that of comparable members.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a36aaec8190b5914c698ba12ee1 |
completed | May 2, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:55 p.m.