Triple
T4555245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joomla! |
E120463
|
entity |
| Predicate | supportsContentVersioning |
P54501
|
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!, supportsContentVersioning, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsContentVersioning Context triple: [Joomla!, supportsContentVersioning, yes]
-
A.
supportsVersioning
chosen
Indicates that the subject provides or is compatible with functionality for managing and maintaining multiple versions of an item or resource.
-
B.
supportsSemanticVersioning
Indicates that one entity adheres to and correctly handles semantic versioning rules for another entity’s versions.
-
C.
earlierVersionsCapability
Indicates that an entity has the ability to access, handle, or interact with earlier versions of another entity or resource.
-
D.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
E.
supportsLanguageVersion
Indicates that one entity provides compatibility with, or can correctly operate using, a specified version of a language.
- 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.