Triple
T4555476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CakePHP |
E120466
|
entity |
| Predicate | stableReleaseMajorVersion |
P10600
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [CakePHP, stableReleaseMajorVersion, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stableReleaseMajorVersion Context triple: [CakePHP, stableReleaseMajorVersion, 4]
-
A.
stableReleaseStatus
Indicates the release status or condition of a stable version of something (such as software or a product).
-
B.
majorVersion
chosen
Indicates that one entity specifies or corresponds to the primary (major) version number of another entity in a versioning scheme.
-
C.
releaseVersion
Indicates the specific version identifier associated with a particular release of something (e.g., software, product, or document).
-
D.
majorRevision
Indicates a substantial change or overhaul made to something, significantly altering its previous form or content.
-
E.
stableReleasesMaintainedBy
Indicates that the stable (non-development) releases of a software project are currently being maintained or supported by a particular entity.
- 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.