Triple
T4555241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joomla! |
E120463
|
entity |
| Predicate | supportsSearchEngineFriendlyURLs |
P57994
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Joomla!, supportsSearchEngineFriendlyURLs, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSearchEngineFriendlyURLs Context triple: [Joomla!, supportsSearchEngineFriendlyURLs, yes]
-
A.
supportsURLBuilding
Indicates that one entity provides the capability or functionality to construct or generate URLs for another entity or process.
-
B.
supportsLinks
Indicates that one entity provides backing, endorsement, or assistance to another entity through connections or references (such as hyperlinks or relational links).
-
C.
supportsRouting
Indicates that one entity provides the capability to determine and direct paths or routes for another entity’s traffic, requests, or messages.
-
D.
defaultSearchEngineOptions
Indicates the configuration settings or choices available for which search engine is used by default.
-
E.
defaultSearchEngine
Indicates that one entity is designated as the primary or standard search engine used by another entity (such as a user, browser, or system) for performing search queries.
- 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_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. |
| PDg | Predicate description generation | batch_69bd56b4a9508190acdb888eef18f1ee |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:09 p.m.