Triple
T20247458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Community Group Report |
E498457
|
entity |
| Predicate | isVersioned |
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: [Community Group Report, isVersioned, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVersioned Context triple: [Community Group Report, isVersioned, yes]
-
A.
versionedAs
Indicates that one entity exists as a specific version or revision of another entity.
-
B.
supportsVersioning
chosen
Indicates that the subject provides or is compatible with functionality for managing and maintaining multiple versions of an item or resource.
-
C.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
D.
hasVersionCount
Indicates the total number of distinct versions associated with a given entity.
-
E.
hasVersionType
Indicates that one entity is associated with a specific kind or category of version of another 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673a3c61481909413e042d76cc580 |
completed | April 20, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:40 p.m.