Triple
T29387801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twenty-One Demands |
E745296
|
entity |
| Predicate | statusOfGroup5 |
P129418
|
FINISHED |
| Object | not fully accepted |
—
|
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: not fully accepted | Statement: [Twenty-One Demands, statusOfGroup5, not fully accepted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfGroup5 Context triple: [Twenty-One Demands, statusOfGroup5, not fully accepted]
-
A.
statusGroup
Indicates a classification relationship where an entity is assigned to or associated with a particular status category or group.
-
B.
hasGroupStatus
chosen
Indicates that an entity possesses a particular status, role, or condition within a group or collective context.
-
C.
ISOGroupingStatus
Indicates the relationship between an entity and its classification or status within an ISO-defined grouping or category.
-
D.
statusOfG1G2G3
Indicates that a specific status or condition is jointly associated with the combination or grouping of entities G1, G2, and G3.
-
E.
classStatus
Indicates the current academic or enrollment standing of an entity within a class or course context.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: April 28, 2026, 2:40 p.m.