Triple
T4555259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joomla! |
E120463
|
entity |
| Predicate | hasDocumentationSite |
P28142
|
FINISHED |
| Object | https://docs.joomla.org |
—
|
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: https://docs.joomla.org | Statement: [Joomla!, hasDocumentationSite, https://docs.joomla.org]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDocumentationSite Context triple: [Joomla!, hasDocumentationSite, https://docs.joomla.org]
-
A.
hasDocumentationAt
chosen
Indicates that something is documented or described in a specific document, file, or location.
-
B.
hasDocumentationStatus
Indicates the current state or condition of documentation associated with an entity, such as whether it exists, is complete, or is up to date.
-
C.
documentedUsing
Indicates that something is recorded, described, or specified by means of a particular document, tool, or documentation method.
-
D.
hasCompanionWebsite
Indicates that something is associated with or supported by a dedicated companion website.
-
E.
hasLimitedDocumentation
Indicates that the subject is associated with documentation that is sparse, incomplete, or not sufficiently detailed.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd5813af948190b10b02dadf6496bf |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd5223423c81908317351b58cff5f5 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.